{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-17506 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-17506 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-17506 is a high-severity cross-site scripting vulnerability in bensibley Independent Analytics – WordPress Analytics Plugin, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-17506 and fix it if it is affected.\n\nWhat it is: CVE-2026-17506 is a high-severity cross-site scripting vulnerability in bensibley Independent Analytics – WordPress Analytics Plugin, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-17506 in the wild and no public exploit code.\n\nAffected product: bensibley Independent Analytics – WordPress Analytics Plugin. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-17506/ (Markdown: https://insights.sbomify.com/CVE-2026-17506/index.md)","id":"CVE-2026-17506","markdown":"https://insights.sbomify.com/CVE-2026-17506/index.md","name":"CVE-2026-17506","record":{"aliases":["GHSA-cv7w-3p2j-xhxx"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress analytics plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject arbitrary web scripts via the 404 tracking parameter, leading to stored XSS execution in WordPress admin pages.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Independent Analytics \u003c= 2.15.0 - Unauthenticated Stored Cross-Site Scripting","id":"CVE-2026-17506","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"MLS membership checks compare a uint32 leaf_index as signed, admitting an out-of-range sender","id":"CVE-2026-17507"},"packages":[],"prev":{"headline":"TranslatePress \u003c= 3.2.5 - Reflected Cross-Site Scripting","id":"CVE-2026-17505"},"products":["Independent Analytics – WordPress Analytics Plugin"],"published":"2026-08-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-05","vendors":["bensibley"]},"summary":"Unauthenticated attackers can inject arbitrary web scripts via the 404 tracking parameter, leading to stored XSS execution in WordPress admin pages.","url":"https://insights.sbomify.com/CVE-2026-17506/"}