CVE-2026-5737: Independent Analytics (WordPress plugin) · Server-Side Request Forgery (SSRF)
Affects Independent Analytics (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| bensibleyIndependent Analytics – WordPress Analytics Plugin | Affected
| Fixed in– |
AI-suggested
Until an official fix is released, users should consider disabling or removing the Independent Analytics plugin if possible. Monitoring for unusual outbound requests from the server may help detect exploitation attempts, but no specific mitigation is provided by the vendor at this time.
Description
The Independent Analytics plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.14.9. This is due to a public tracking route at /wp-json/iawp/search that accepts attacker-controlled referrer_url values when the signature matches, combined with a scheduled favicon fetcher that performs unrestricted cURL requests to stored domains. The signature validation is insufficient because the signature is embedded in publicly-accessible JavaScript and the salt is static per site, allowing attackers to extract valid signatures. The favicon downloader uses raw cURL functions without any SSRF protection mechanisms (no localhost blocking, no private network filtering, and does not use WordPress's wp_safe_remote_* functions). This makes it possible for unauthenticated attackers to inject malicious referrer domains into the database and trigger server-side requests to arbitrary hosts including internal services.
References
- wordfence.com/threat-intel/vulnerabilities/id/06ecc40c-6a63-4354-9f49-1925896622f5?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/independent-analytics/trunk/IAWP/Favicon/FaviconDownloader.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/independent-analytics/tags/2.14.4/IAWP/Favicon/FaviconDownloader.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/independent-analytics/trunk/IAWP/REST_API.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/independent-analytics/tags/2.14.4/IAWP/REST_API.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/independent-analytics/trunk/IAWP/Views/View.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/independent-analytics/tags/2.14.4/IAWP/Views/View.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/independent-analytics/trunk/IAWP/FetchFaviconsJob.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/independent-analytics/tags/2.14.4/IAWP/FetchFaviconsJob.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3537814%40independent-analytics&new=3537814%40independent-analytics&sfp_email=&sfph_mail= (opens in a new tab)