Rank Math Vulnerability: Fixed in August, Disclosed in October
By WP Vanguard Team
Rank Math SEO 1.0.277, released on August 26, 2026, fixed nine CVEs, and two of them score 8.8: an Author+ remote code execution bug (CVE-2026-81757) and a Contributor+ PHP object injection (CVE-2026-1928). The changelog line for all of it read "Strengthened the security of the plugin."
Eight of the nine advisories appeared between August 27 and September 3. CVE-2026-1928 didn't go public until October 27, 62 days after the fix shipped. If a site updated in that time, the bug was already closed. If it didn't, the details of an object injection in a plugin with 4,000,000 installs have now been public for more than a week.
On this page
- Aug 261.0.277Changelog: strengthened the security
- Aug 27 - Sep 38 CVEsAdvisories for the same release
- Oct 8 - 141.0.280Four more, mostly admin-level
- Oct 27CVE-2026-1928Contributor+ object injection published
- Nov 31.0.281Current release
What Rank Math 1.0.277 fixed
Here are the nine CVEs our database lists against 1.0.277 (and 1.0.277.1 for one of them). The titles come from the Wordfence feed.
| CVE | CVSS | Published | Advisory title |
|---|---|---|---|
| CVE-2026-81757 | 8.8 | Aug 27 | Authenticated (Author+) remote code execution |
| CVE-2026-77786 | 2.7 | Aug 29 | Missing authorization |
| CVE-2026-77788 | 4.3 | Aug 31 | Author+ arbitrary post and user meta overwrite |
| CVE-2026-77782 | 5.3 | Aug 31 | Unauthenticated password-protected post content disclosure (fixed in 1.0.277.1) |
| CVE-2026-77783 | 5.3 | Sep 2 | Unauthenticated information exposure |
| CVE-2026-77785 | 4.3 | Sep 2 | Author+ information exposure |
| CVE-2026-77787 | 4.3 | Sep 2 | Missing authorization |
| CVE-2026-77784 | 4.3 | Sep 3 | Author+ SEO object updates |
| CVE-2026-1928 | 8.8 | Oct 27 | Contributor+ PHP object injection to remote code execution |
Rank Math went on to fix four more in 1.0.280, published October 8 to 14, and those are mostly Administrator+ bugs. That makes 13 CVEs across the two releases. The low scores are mostly authorization checks. The two 8.8 entries matter more, because they can lead to code running on the server.
The release was a feature release. The changelog leads with a new Support Agent and settings abilities for AI assistants, adds an llms.txt filter, and lists fixes for the setup wizard import, local business schema output and the Classic Editor link search. The security line sits last, with credit to Patchstack, Project Black, Mohammed Abd Alrahman and Usama Arshad.
Key finding
Two of the nine fixes score 8.8, and the changelog named none of them. A site owner who reads changelogs to decide what to update first would have filed 1.0.277 as a feature release.
What we found in the 1.0.277 patch
We diffed tags 1.0.276 and 1.0.277 in the public WordPress.org SVN repository. The release changes 116 files: 44 modified, 71 added and one removed. We found three security-relevant changes, all in includes/rest/class-shared.php. We haven't audited the other files line by line, so there may be more.
1. The update path never checked who owned the meta row. The schema endpoint takes a list of schemas keyed by meta ID. For existing schemas, 1.0.276 took the numeric ID from the request and called update_metadata_by_mid() on it, with no check that the row belonged to the post being edited. The delete path in the same file already had that check. 1.0.277 adds it to the update path, with the comment "Bail if the meta id doesn't belong to the authorized object."
2. The delete path unserialized a value twice. WordPress core's get_metadata_by_mid() already runs maybe_unserialize() on the value it returns. Rank Math's delete code then ran maybe_unserialize() on that result again. 1.0.277 removes the second call. A value that is still a serialized string after the first decode would be turned into an object by the second.
3. Schema for unpublished posts was readable. A new can_view_schema_post() check refuses to return schema for drafts, private posts, scheduled posts and password-protected posts unless the requester can read the post.
Our mapping to advisories is a reading of titles, not a statement from Rank Math or Wordfence. Change 1 fits CVE-2026-77788 (meta overwrite). Change 2 fits CVE-2026-1928 (object injection). Change 3 fits the two disclosure CVEs from August 31 and September 2. We haven't traced which edit closes the Author+ code execution bug, and we haven't built an exploit for any of them.
The permission check for the schema endpoint requires the Schema module to be active, the onpage_snippet capability and edit access to the object. That fits the advisory's Contributor-and-above wording, not any logged-in user.
What the changelog hid and the advisories didn't
The changelog gave a site owner nothing to act on. The advisory feeds did better. The Author+ code execution advisory appeared on August 27, the day after release, so anyone watching advisories had a reason to update within a day. Anyone using the changelog to judge urgency had none.
CVE-2026-1928 is the one that trailed. We can't see why the object injection reached the feed two months after the other eight, and Wordfence's date is the only one we have.
We've seen a gap like this before. ProfilePress shipped a fix for a shortcode injection 11 days before its CVE went public, and the changelog showed five releases closing five different fields, as we covered in the ProfilePress analysis. Rank Math's gap on CVE-2026-1928 is more than five times longer.
None of this means Rank Math did something unusual. Vendors often keep security wording vague so a changelog doesn't act as a map for attackers who diff releases. That's a fair instinct. It leaves site owners depending on update habits and advisory feeds, not on the changelog.
For context, our database holds 215 high or critical PHP object injection disclosures dated August 1 or later. Our look at three recent unserialize fixes covers how the bug class works. This one is a good example of it: the second maybe_unserialize() looks harmless on its own, because the first one hid the fact that the value was already decoded.
What to do about Rank Math now
- Update to 1.0.281 or later. 1.0.280 closed four more bugs and 1.0.277.1 closed the password-protected content leak, so stopping at 1.0.277 leaves some open.
- Confirm the version on every site. Run
wp plugin get seo-by-rank-math --field=version, or check the Plugins screen. Don't assume auto-updates ran, because WordPress doesn't turn them on for plugins by default. - Don't rely on switching off the Schema module. The double-unserialize sits in delete code that the general metadata endpoint also calls, and in the 1.0.276 code we read, that path doesn't check whether the Schema module is active. We can't point to a setting that closes it. Update.
- Look at who holds Contributor and Author roles. Run
wp user list --role=contributor --fields=ID,user_login,user_registeredand repeat it forauthor. An account you don't recognize is the one worth checking. Our guide to subscriber-level bugs and open registration explains why that bar is lower than it sounds. - Turn on auto-updates for plugins you can't afford to leave behind. On the Plugins screen, use "Enable auto-updates" for Rank Math. Here the fix existed for 62 days before the advisory, so a site with auto-updates on was patched long before it was published.
This is a different story from the Rank Math PRO malware incident in October. That was a compromised premium package. This is a vulnerability in the free plugin from August.
Check your own sites
A surface scan is free and matches your installed Rank Math version against our vulnerability database, including all 13 entries above. The free deep scan goes inside the server over SSH and looks at files, users and the database, which is where an attack through a Contributor account would leave traces. For a repeatable process across many sites, see how to check WordPress plugins for known vulnerabilities.
The rest of this week's critical updates are in the plugins to patch this week.
References
- Wordfence Intelligence: CVE-2026-1928, Rank Math SEO 1.0.276 Contributor+ PHP Object Injection
- Rank Math SEO changelog on WordPress.org
- WordPress.org plugin repository: diff of tags 1.0.276 and 1.0.277
- WordPress core: get_metadata_by_mid()
- NVD: CVE-2026-1928
- NVD: CVE-2026-81757
- Rank Math SEO in the WP Vanguard vulnerability database
Check your WordPress site security
Free scan, no login required. Find vulnerabilities before attackers do.
Scan your site freeRelated reading
Get weekly WordPress security tips
Vulnerability alerts, plugin updates, and security guides. No spam. Unsubscribe any time.