CVE-2026-5737

Independent Analytics <= 2.14.9 - Unauthenticated Server-Side Request Forgery via Tracking Route

2026-05-27 14:52
alex_henry20

Strategic Overview

Status
Patched in 2.14.10
Affected Version
<= 2.14.9
CVSS
6.5Medium
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2026-5737
View all Independent Analytics – WordPress Analytics Plugin vulnerabilities

At a glance

CVE-2026-5737 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the Independent Analytics WordPress plugin, affecting versions <= 2.14.9. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.14.10; sites on affected versions should update now. Disclosed May 2026, reported by alex_henry20.

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-918: Server-Side Request Forgery (SSRF)

Reaching this weakness in Independent Analytics <= 2.14.9 takes no account at all. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.

The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For Independent Analytics the fix is 2.14.10: builds <= 2.14.9 are affected, anything from 2.14.10 onward is not.

Remediation

Update to version 2.14.10, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Independent Analytics 2.14.10 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C