WordPress security changelog
MEDIUM CVE-2026-5737 Deferred

Independent Analytics – WordPress Analytics Plugin: Server-side request forgery

Independent Analytics – WordPress Analytics Plugin is affected by server-side request forgery. The vulnerable path is reachable without authentication. The vulnerable server can be induced to make attacker-selected network requests. The published affected range is <= 2.14.9.

CVE / CNA score 6.5 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Independent Analytics – WordPress Analytics Plugin
Plugin slug
independent-analytics
Affected
<= 2.14.9
Safe version
See mitigation notes
Published
May 28, 2026
Weakness
CWE-918 — Server-Side Request Forgery (SSRF)

This CVE was published May 28, 2026 and is one of 2 known issues for this plugin.

What to do

Update, patch or deactivate.

No fixed release is identified. Update Independent Analytics – WordPress Analytics Plugin when a release after 2.14.9 becomes available; until then, disable and remove it when the site's risk warrants. The official upstream changelog lists version 2.15.4, which is newer than the published affected range. Its changelog does not clearly confirm this specific fix, so it is not counted as a known-safe release.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical 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.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

References

Primary and upstream sources