CVE-2026-81757 is a remote code execution (RCE) vulnerability in Rank Math SEO affecting version 1.0.276 and earlier. Patchstack published the issue on August 27, 2026, and identifies Rank Math SEO 1.0.277 as the patched release. According to the advisory, exploitation requires a WordPress account with the Author role or higher.
Rank Math is present on roughly 4 million installations, so the potential reach is large. That does not mean four million sites were attacked. A site is exposed only when it runs an affected version and an attacker controls an Author-level account or a custom role with equivalent capabilities.
Immediate action: check the installed version and update Rank Math SEO to 1.0.277 or later. If you cannot update today, temporarily deactivate the plugin, review publishing accounts, and monitor unexpected changes to files, users, and plugins.
CVE-2026-81757 at a glance
| Item | Confirmed information |
|---|---|
| Affected software | Rank Math SEO for WordPress |
| Affected versions | 1.0.276 and earlier |
| Patched version | 1.0.277 |
| Vulnerability type | Remote code execution through deserialization of untrusted data |
| CWE | CWE-502: Deserialization of Untrusted Data |
| Required privileges | Author or higher, according to Patchstack |
| CVSS | 7.2/10, High severity |
| User interaction | None after the attacker controls a sufficiently privileged account |
| Confirmed exploitation | No public confirmation as of August 28, 2026 |
What is the Rank Math SEO vulnerability?
The Patchstack advisory classifies CVE-2026-81757 as authenticated RCE and associates it with deserialization of untrusted data. Deserialization converts stored or received data into objects PHP can use. If an application accepts manipulated serialized data without strict validation, a crafted object may trigger behavior the developer did not intend.
The worst-case result is arbitrary PHP code execution on the server. An attacker could install persistence, alter the site, steal information, create administrators, redirect visitors, or abuse server resources. The public record does not provide a complete exploitation path, so it would be inaccurate to invent endpoints, parameters, or indicators that have not been disclosed.
This is not a WordPress core vulnerability. It affects the Rank Math SEO plugin. A site without that plugin is not vulnerable to CVE-2026-81757, although it still needs timely core, theme, and plugin updates.
What is the real-world exposure today?
Patchstack lists approximately 4 million Rank Math SEO installations. That number describes the plugin’s install base, not the number of vulnerable or compromised websites. Actual exposure requires all of the following:
- Rank Math SEO is installed and active.
- The installed version is 1.0.276 or earlier.
- The attacker controls an Author account or a custom role with comparable privileges.
The CVSS vector records high privileges because the issue does not begin with a fully anonymous visitor. It still matters for publishers, stores, agencies, membership sites, and any WordPress installation with multiple contributors. A reused password, stolen session, or forgotten former-contributor account can supply the foothold.
As of August 28, 2026, public sources did not confirm active exploitation, and CVE-2026-81757 was not in the CISA Known Exploited Vulnerabilities catalog. The CVE record marked exploitation as none. That is not the same as zero risk: Patchstack rates the issue High priority and warns that vulnerabilities of this class can become mass-exploitation targets. A patch is already available, so delaying offers no practical benefit.
How to check whether your WordPress site is affected
Check from the WordPress dashboard
- Open Plugins → Installed Plugins.
- Find Rank Math SEO.
- Read the installed version.
- If it shows 1.0.276 or earlier, update the site.
- Open Users → All Users and verify every Author, Editor, and Administrator.
A current WordPress core version does not guarantee a safe plugin version. Plugins have independent release and update cycles.
Check with WP-CLI
wp plugin get seo-by-rank-math --fields=name,status,version
wp plugin verify-checksums seo-by-rank-mathA safe result should show 1.0.277 or later. Checksum verification can flag files that differ from the official package, but it does not prove the whole site is clean. An intruder may modify another plugin, the theme, mu-plugins, uploads, or database records.
On WordPress Multisite, check network activation and every managed instance. Agencies should inventory all customer sites rather than checking only a primary domain.
How to update Rank Math SEO safely
From the dashboard
- Create a current backup of files and the database.
- Open Dashboard → Updates or the installed plugin list.
- Update Rank Math SEO.
- Confirm that the displayed version is 1.0.277 or later.
- Purge WordPress, plugin, proxy, and CDN caches where applicable.
- Test the homepage, posts, XML sitemap, and redirects.
With WP-CLI
wp plugin update seo-by-rank-math
wp plugin get seo-by-rank-math --field=version
wp cache flushThe version command should return 1.0.277 or a later release. If you also use Rank Math PRO, install the current licensed build and verify compatibility between the Free and PRO editions.
What if you cannot update immediately?
Installing the fixed release is the permanent solution. While resolving a compatibility problem or waiting for a maintenance window, reduce exposure by deactivating Rank Math:
Keep WordPress in an environment that is easier to manage
Host your site on Teramont Web Hosting with a control panel and resources prepared for keeping WordPress current.
wp plugin deactivate seo-by-rank-math
wp plugin status seo-by-rank-mathDeactivation can temporarily remove sitemap, redirect, or metadata functionality. Document the change and retest the site. Patchstack says it has released a virtual mitigation rule; a WAF can add defense in depth, but it does not replace the software update.
Disable unused Author accounts, reset contributor credentials, and require multi-factor authentication where available. Do not remove roles indiscriminately on an editorial site; first identify who genuinely needs publishing access.
How to look for possible compromise
There is no single public indicator that proves CVE-2026-81757 exploitation. Look for several signals and compare the current state against backups, logs, and approved changes.
wp user list --fields=ID,user_login,user_email,roles,user_registered
wp plugin list --status=active
wp core verify-checksums
wp plugin verify-checksums --all
find wp-content/uploads -type f -name '*.php' -printInvestigate:
- New users or unauthorized role changes.
- Unknown plugins, unexpected mu-plugins, or disabled security tools.
- Recent PHP files under
wp-content/uploads. - Unplanned edits to
wp-config.php,.htaccess, the active theme, or scheduled tasks. - Redirects, popups, SEO spam, or pages that do not appear in the normal editor.
- Author sessions from unusual locations or times.
These commands are a first-pass review, not complete forensics. Checksums also do not cover custom files or every database change.
What to do if you find signs of intrusion
- Preserve evidence: copy files, the database, and logs before cleanup.
- Contain the site: enable maintenance mode or restrict traffic if it is serving malware.
- Restore from a known-good backup: deleting one suspicious file is not enough.
- Patch everything: Rank Math, WordPress core, themes, and other plugins.
- Remove unknown accounts and extensions after documenting them.
- Rotate credentials: WordPress administrators, hosting panel, SFTP/SSH, and database access where appropriate.
- Refresh authentication salts to invalidate existing WordPress cookies.
wp config shuffle-salts
wp cache flushIf the site processes payments, personal data, or regulated information, consider professional incident response and applicable notification duties. A repaired homepage does not prove that persistence is gone.
Reducing the impact of future WordPress vulnerabilities
- Enable automatic updates for trusted plugins or establish a daily patch window.
- Keep off-site backups and test restoration.
- Apply least privilege: a writer does not need Administrator access.
- Remove unused plugins and user accounts.
- Protect logins with unique passwords and MFA.
- Centralize logs and alerts for file, user, and plugin changes.
- Test updates in staging for critical sites, but do not delay an RCE patch for days.
Hosting cannot automatically fix vulnerable plugin code, but a manageable environment can shorten recovery time. For a panel-based WordPress site, review Teramont Web Hosting. Agencies and operators that need root access, automation, and server-level visibility can compare VPS Hosting.
Frequently asked questions
Does CVE-2026-81757 affect WordPress core?
No. It affects Rank Math SEO through version 1.0.276. A site without that plugin is not exposed to this specific CVE.
Can it be exploited without logging in?
Patchstack lists Author privileges as a requirement. The attacker must control that role or a more privileged account; this is not described as fully unauthenticated RCE.
Is Rank Math 1.0.277 safe?
Patchstack identifies 1.0.277 as the first patched release for CVE-2026-81757. Install that version or later.
Is it already being exploited?
As of August 28, 2026, there was no public confirmation of active exploitation and the CVE was not in CISA KEV. The status can change, so a lack of confirmed attacks is not a reason to postpone updating.
Does deactivating Rank Math remove an existing infection?
No. It temporarily reduces the plugin’s attack surface. If code execution already occurred, review or restore the site, rotate credentials, and hunt for persistence.
You should also review CVE-2026-32566 in ACPT Pro. Unlike this Rank Math flaw, the ACPT Pro vulnerability requires no authentication and still had no official patch as of August 28, 2026.
Conclusion
CVE-2026-81757 combines potentially severe impact with an important limiting condition: Rank Math SEO runs on millions of sites, but the attacker needs an Author-level account or higher. The proportionate response is neither panic nor dismissal. Check the version, update to 1.0.277 or later, and inspect users and files if there is any reason to suspect unauthorized access.
