CVE-2026-17506
CVE-2026-17506 — Independent Analytics <= 2.15.0 - Unauthenticated Stored Cross-Site Scripting
The Independent Analytics plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 404 not_found_url tracking parameter in versions up to, and including, 2.15.0. This is due to the get_cell_content() function applying urldecode() after esc_url() when rendering the URL column for 404 entries — a sequence that allows percent-encoded HTML to pass URL validation and then be reconstructed as raw markup, which wp_kses_post() does not strip because it retains img elements and data-* attributes, and because the public REST endpoint /iawp/search accepts unauthenticated requests as long as they carry a signature that is itself embedded in public page HTML. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Published Updated Sources: cvelistV5, Wordfence
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
0%
chance of exploitation in 30 days
CVSS base
7.2
HIGH
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script all four kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 7.2 | CVSS 3.1 | HIGH | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-79
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Search application, proxy, and WAF logs for requests touching /iawp/search.
References
7 on the record
- www.wordfence.com/threat-intel/vulnerabilities/id/90ea5c51-e739-42c1-a276-851ad800ff00?source=cve
reference
- plugins.trac.wordpress.org/browser/independent-analytics/tags/2.15.0/IAWP/Tables/Table.php#L142
reference
- plugins.trac.wordpress.org/browser/independent-analytics/tags/2.15.0/IAWP/REST_API.php#L458
reference
- plugins.trac.wordpress.org/browser/independent-analytics/tags/2.15.0/IAWP/REST_API.php#L86
reference
- plugins.trac.wordpress.org/browser/independent-analytics/tags/2.15.0/IAWP/Resource_Identifier.php#L126
reference
- plugins.trac.wordpress.org/browser/independent-analytics/tags/2.15.0/IAWP/Views/View.php#L206
reference
- plugins.trac.wordpress.org/changeset?reponame=&new=3627446%40independent-analytics%2Ftrunk%2FIAWP%2FUtils%2FRequest.php&old=3618630%40independent-analytics%2Ftrunk%2FIAWP%2FUtils%2FRequest.php
reference
Elsewhere on this site
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.