# CVE-2026-1928: Rank Math SEO <= 1.0.276 - Authenticated (Contributor+) PHP Object Injection to Remote Code Execution


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-f7v4-wpwr-74r2

## What is CVE-2026-1928?

CVE-2026-1928 is a high-severity vulnerability in rankmath Rank Math SEO – AI SEO Tools to Dominate SEO Rankings, published on 28 Oct 2026. 

### Official description

The Rank Math SEO – AI SEO Tools to Dominate SEO Rankings plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.0.276 via deserialization of untrusted input in the updateMeta REST API endpoint. This makes it possible forauthenticated attackers, with Contributor-level access and above, to inject a PHP Object. The additional presence of a POP chain allows attackers to achieve remote code execution by writing a webshell to the uploads directory.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-1928?


## How do I fix CVE-2026-1928?

No fix has been published for CVE-2026-1928 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-1928 being exploited?

There is no known exploitation of CVE-2026-1928 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1928 and fix it if it is affected.

What it is: CVE-2026-1928 is a high-severity vulnerability in rankmath Rank Math SEO – AI SEO Tools to Dominate SEO Rankings, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-1928 in the wild and no public exploit code.

Affected product: rankmath Rank Math SEO – AI SEO Tools to Dominate SEO Rankings. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1928/ (Markdown: https://insights.sbomify.com/CVE-2026-1928/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1928
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1928
- OSV: https://osv.dev/vulnerability/CVE-2026-1928

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1928/
Summaries are generated and may contain mistakes; the official description above is the record.