# CVE-2026-84936: EmbedPress 4.6.0 - 4.6.3 - Unauthenticated Google Reviews API Quota Consumption and Database Bloat

> Unauthenticated attackers can trigger excessive API costs and database bloat in EmbedPress by exploiting missing authorization on review loading.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 5 Sep 2026
- **Updated:** 6 Sep 2026
- **Also known as:** GHSA-5cvh-x6xg-5fhw

## What is CVE-2026-84936?

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

### Official description

The EmbedPress  WordPress plugin before 4.6.4 does not have proper authorization on a public review-loading action, allowing unauthenticated users to force the site to make repeated billable third-party API requests using the site's own configured API key, and to create an unbounded number of attacker-controlled rows in the database.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-84936 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84936 is a medium-severity missing authorization vulnerability in Unknown EmbedPress, published on 5 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-84936 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-84936/ (Markdown: https://insights.sbomify.com/CVE-2026-84936/index.md)
```

## Sources

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

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