{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-5737 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-5737 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-5737 is a medium-severity server-side request forgery vulnerability in bensibley Independent Analytics – WordPress Analytics Plugin, published on 28 May 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-5737 and fix it if it is affected.\n\nWhat it is: CVE-2026-5737 is a medium-severity server-side request forgery vulnerability in bensibley Independent Analytics – WordPress Analytics Plugin, published on 28 May 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-5737 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-5737/ (Markdown: https://insights.sbomify.com/CVE-2026-5737/index.md)","id":"CVE-2026-5737","markdown":"https://insights.sbomify.com/CVE-2026-5737/index.md","name":"CVE-2026-5737","record":{"aliases":["GHSA-hq3c-7r96-pf8g"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress analytics plugin","requires_auth":"none","summary":"Unauthenticated attackers can exploit insufficient signature validation and unsafe cURL usage to perform server-side requests to arbitrary internal hosts.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"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.","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.14.9 - Unauthenticated Server-Side Request Forgery via Tracking Route","id":"CVE-2026-5737","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":10,"next":{"headline":"Reflected XSS in BilPark's DoXBASE","id":"CVE-2026-5738"},"packages":[],"prev":{"headline":"PowerJob detailPlus Endpoint InstanceController.java sql injection","id":"CVE-2026-5736"},"products":["Independent Analytics – WordPress Analytics Plugin"],"published":"2026-05-28","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-05-28","vendors":["bensibley"]},"summary":"Unauthenticated attackers can exploit insufficient signature validation and unsafe cURL usage to perform server-side requests to arbitrary internal hosts.","url":"https://insights.sbomify.com/CVE-2026-5737/"}