# CVE-2026-82925: Site Reviews 7.2.2 - 8.2.2 - Unauthenticated PHP Object Injection via Form Signature

> Unauthenticated attackers can inject PHP objects via form signatures on sites with weak nonce keys, potentially leading to code execution.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-3237-mv84-xmm9

## What is CVE-2026-82925?

CVE-2026-82925 is a high-severity unsafe deserialization vulnerability in Unknown Site Reviews, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Site Reviews WordPress plugin before 8.3.0 does not prevent request data from being deserialized, and derives the key protecting that data by padding out the site's WordPress nonce key, which makes the key publicly computable on installs where that key is absent, left at its sample value, or too short to be secret. This allows unauthenticated users to inject arbitrary PHP objects on such installs. The Site Reviews WordPress plugin before 8.3.0's own code contains no chain onward from the injected object, so how far it reaches depends on the other code present on the site.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-82925 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82925 is a high-severity unsafe deserialization vulnerability in Unknown Site Reviews, published on 10 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-82925 in the wild and no public exploit code.

Affected product: Unknown Site Reviews. 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-82925/ (Markdown: https://insights.sbomify.com/CVE-2026-82925/index.md)
```

## Sources

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

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