# CVE-2026-77783: Rank Math SEO < 1.0.277 - Unauthenticated Non-Public Post Schema and Content Disclosure

> Unauthenticated attackers can view schema and content of non-public posts in Rank Math SEO plugin.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-597x-94h4-64xw

## What is CVE-2026-77783?

CVE-2026-77783 is a low-severity vulnerability in Unknown Rank Math SEO, published on 2 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Rank Math SEO  WordPress plugin before 1.0.277 does not verify that the post whose schema it renders on the front end is publicly viewable, allowing unauthenticated visitors to disclose the schema and associated content of draft, pending, private, scheduled and password-protected posts.

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

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


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

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

## Is CVE-2026-77783 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77783 is a low-severity vulnerability in Unknown Rank Math SEO, published on 2 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-77783 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-77783/ (Markdown: https://insights.sbomify.com/CVE-2026-77783/index.md)
```

## Sources

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

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