# CVE-2026-84927: EmbedPress 4.6.0 - 4.6.3 - Contributor+ Google Reviews Modification

> Contributors can modify site-wide Google Reviews settings via an insecure REST API route, allowing unauthorized data injection and deletion.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/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:** 5 Sep 2026
- **Updated:** 6 Sep 2026
- **Also known as:** GHSA-6rmc-pw7c-rvpw

## What is CVE-2026-84927?

CVE-2026-84927 is a low-severity missing authorization vulnerability in Unknown EmbedPress, published on 5 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The EmbedPress  WordPress plugin before 4.6.4 does not perform a sufficient authorization check on one of its Google Reviews REST API routes, allowing users with the Contributor role and above to modify a site-wide store, deleting entries an administrator configured and injecting their own, which are rendered publicly across the site.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-84927 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84927 is a low-severity missing authorization vulnerability in Unknown EmbedPress, published on 5 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-84927 in the wild and no public exploit code.

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

## Sources

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

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