# CVE-2026-77785: Rank Math SEO < 1.0.277 - Author+ Non-Public Post Content Disclosure via Abilities API

> Authors can read non-public posts from other users due to missing authorization checks in the Rank Math SEO plugin.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-r8jc-g7jp-q2rh

## What is CVE-2026-77785?

CVE-2026-77785 is a low-severity missing authorization vulnerability in Unknown Rank Math SEO, published on 2 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Rank Math SEO  WordPress plugin before 1.0.277 does not verify that the requesting user is permitted to read the specific post referenced in a request before returning its content and SEO metadata, allowing users with the Author role and above to read the title, body and metadata of other users' non-public posts.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-77785 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77785 is a low-severity missing authorization vulnerability in Unknown Rank Math SEO, published on 2 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-77785 in the wild and no public exploit code.

Affected product: Unknown Rank Math SEO. 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-77785/ (Markdown: https://insights.sbomify.com/CVE-2026-77785/index.md)
```

## Sources

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

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