# CVE-2026-92099: WPGraphQL Smart Cache < 2.3.2 - Unauthenticated Persisted Query Registration and Alias Squatting

> Unauthenticated attackers can register arbitrary persisted queries and claim aliases in WPGraphQL Smart Cache, potentially disrupting site functionality or bypassing intended access controls.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Sep 2026
- **Updated:** 19 Sep 2026

## What is CVE-2026-92099?

CVE-2026-92099 is a medium-severity missing authorization vulnerability in Unknown WPGraphQL Smart Cache, published on 19 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WPGraphQL Smart Cache WordPress plugin before 2.3.2 does not require authorisation or validate a caller-supplied query identifier before storing a persisted query from a request, allowing unauthenticated users to publish arbitrary query documents and claim query aliases before a site's own frontend registers them.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-92099 being exploited?

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

Public exploit code:

- PoC for CVE-2026-92099 on WPGraphQL Smart Cache (github_poc): https://github.com/MS-0x404/CVE-2026-92099

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92099 is a medium-severity missing authorization vulnerability in Unknown WPGraphQL Smart Cache, published on 19 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-92099 in the wild and no public exploit code.

Affected product: Unknown WPGraphQL Smart Cache. 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-92099/ (Markdown: https://insights.sbomify.com/CVE-2026-92099/index.md)
```

## Sources

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

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