{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97640 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-97640 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-97640 is a high-severity cross-site scripting vulnerability in smub WPConsent – Cookie Banner \u0026 Cookie Consent for Privacy Compliance (GDPR / CCPA / EU Compliance Cookie Notice), published on 16 Oct 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-97640 and fix it if it is affected.\n\nWhat it is: CVE-2026-97640 is a high-severity cross-site scripting vulnerability in smub WPConsent – Cookie Banner \u0026 Cookie Consent for Privacy Compliance (GDPR / CCPA / EU Compliance Cookie Notice), published on 16 Oct 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-97640 in the wild and no public exploit code.\n\nAffected product: smub WPConsent – Cookie Banner \u0026 Cookie Consent for Privacy Compliance (GDPR / CCPA / EU Compliance Cookie Notice). 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-97640/ (Markdown: https://insights.sbomify.com/CVE-2026-97640/index.md)","id":"CVE-2026-97640","markdown":"https://insights.sbomify.com/CVE-2026-97640/index.md","name":"CVE-2026-97640","record":{"aliases":["GHSA-4m2x-3wp6-xmxj"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject arbitrary scripts via comments in WPConsent plugin if Script Blocking is enabled, leading to stored XSS.","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 WPConsent – Cookie Banner \u0026 Cookie Consent for Privacy Compliance (GDPR / CCPA / EU Compliance Cookie Notice) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content via Simple HTML DOM Parser Noise-Key Restoration (mXSS) in all versions up to, and including, 1.1.9 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the Script Blocking feature to be enabled, and the exploit chain depends on an attacker submitting two coordinated comments — one embedding event-handler syntax inside an allowed \u0026lt;code\u0026gt; element and one placing the deterministic ___noise___ restoration key inside an allowed \u0026lt;abbr title=\"\"\u0026gt; attribute — with the key offset confirmable via an unauthenticated wpconsent_debug=1 request.","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":"Cross-site scripting in WPConsent – Cookie Banner \u0026 Cookie Consent for Privacy Compliance (GDPR / CCPA / EU Compliance Cookie Notice)","id":"CVE-2026-97640","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Relevanssi \u003c= 4.28.3 - Unauthenticated Stored Cross-Site Scripting via Comment Content","id":"CVE-2026-97641"},"packages":[],"prev":{"headline":"JSON API Auth \u003c= 3.1.2 - Unauthenticated Authentication Bypass via Cached 'generate_auth_cookie' Response","id":"CVE-2026-97637"},"products":["WPConsent – Cookie Banner \u0026 Cookie Consent for Privacy Compliance (GDPR / CCPA / EU Compliance Cookie Notice)"],"published":"2026-10-16","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["smub"]},"summary":"Unauthenticated attackers can inject arbitrary scripts via comments in WPConsent plugin if Script Blocking is enabled, leading to stored XSS.","url":"https://insights.sbomify.com/CVE-2026-97640/"}