Quick answers
- Is CVE-2026-84926 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84926 being exploited in the wild.
- How severe is CVE-2026-84926?
- Low severity, with a CVSS score of 2.7, published 5 September 2026.
- Which products and versions are affected?
- EmbedPress EmbedPress 4.6.0 - 4.6.3.
- Is there a fix for CVE-2026-84926?
- A patch was published on 2026-09-04: Fixed in version 4.6.4 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-84926 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-84926?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authorization bypass (CWE-200: Exposure of Sensitive Information) in the Google Reviews REST API endpoint `/wp-json/embedpress/v1/google-reviews/managed/status`. The endpoint requires authentication (REST nonce) but fails to enforce admin-only access controls, allowing any authenticated user with contributor-level privileges or above to call it. The response JSON includes the site's admin_email field, which is normally restricted to administrators. An attacker needs a valid contributor account on the WordPress site; no CSRF or privilege escalation chain is required. The vulnerability affects EmbedPress versions 4.6.0 through 4.6.3 and was fixed in version 4.6.4.
Affected products
- EmbedPress EmbedPress 4.6.0 - 4.6.3
Timeline
- 2026-09-03: disclosed
- 2026-09-04: patched: Fixed in version 4.6.4