Quick answers
- Is CVE-2026-10526 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-10526 being exploited in the wild.
- How severe is CVE-2026-10526?
- Medium severity, with a CVSS score of 5.8, published 4 August 2026.
- Which products and versions are affected?
- EmbedPress EmbedPress before 4.6.1.
- Is there a fix for CVE-2026-10526?
- A patch was published on 2026-07-27: Fixed in version 4.6.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-10526 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-10526?
- 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 a blind Server-Side Request Forgery (SSRF) in EmbedPress versions before 4.6.1. The plugin accepts user-supplied URLs via unauthenticated REST API endpoints and admin-ajax.php without proper validation, then fetches these URLs using WordPress's wp_safe_remote_get function. While WordPress core blocks RFC 1918 private ranges and loopback addresses, it does not block link-local (169.254.0.0/16), CGNAT (100.64.0.0/10), or benchmark (198.18.0.0/15) ranges. Attackers can exploit this to reach the AWS metadata service endpoint (169.254.169.254) or other internal targets. The response body is not returned to the attacker, but the outbound request can be confirmed via timing analysis. The vulnerability is fixed in version 4.6.1.
Affected products
- EmbedPress EmbedPress before 4.6.1
Timeline
- 2026-07-27: disclosed: Publicly disclosed on WPScan
- 2026-07-27: patched: Fixed in version 4.6.1
- 2026-08-04: advisory: Published on NVD