{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-13360 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-13360 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-13360 is a high-severity cross-site scripting vulnerability in wplegalpages WPLP Cookie Consent – Cookie Banner \u0026 Consent Management for GDPR, CCPA \u0026 Google Consent Mode, published on 15 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-13360 and fix it if it is affected.\n\nWhat it is: CVE-2026-13360 is a high-severity cross-site scripting vulnerability in wplegalpages WPLP Cookie Consent – Cookie Banner \u0026 Consent Management for GDPR, CCPA \u0026 Google Consent Mode, published on 15 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-13360 in the wild and no public exploit code.\n\nAffected product: wplegalpages WPLP Cookie Consent – Cookie Banner \u0026 Consent Management for GDPR, CCPA \u0026 Google Consent Mode. 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-13360/ (Markdown: https://insights.sbomify.com/CVE-2026-13360/index.md)","id":"CVE-2026-13360","markdown":"https://insights.sbomify.com/CVE-2026-13360/index.md","name":"CVE-2026-13360","record":{"aliases":["GHSA-wj5r-wjwf-mg3q"],"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":"Authenticated users can inject scripts via the regionArray parameter if Google Consent Mode 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 Cookie Banner for GDPR / CCPA – WPLP Cookie Consent plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'regionArray' parameter in all versions up to, and including, 4.3.5 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. Successful exploitation requires that the site administrator has enabled the 'Support Google Consent Mode (GCM)' setting, which is disabled by default. Additionally, the AJAX handler performs no nonce or capability check, allowing any authenticated user including those with Subscriber-level access to overwrite the affected plugin setting.","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 WPLP Cookie Consent – Cookie Banner \u0026 Consent Management for GDPR, CCPA \u0026 Google Consent Mode","id":"CVE-2026-13360","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"IBM Informix Server Vulnerability in SQL Interface Handler Could Allow Remote Code Execution","id":"CVE-2026-13361"},"packages":[],"prev":{"headline":"Cross-site scripting in Contact Form to DB by BestWebSoft – Messages Database Plugin For WordPress","id":"CVE-2026-13359"},"products":["WPLP Cookie Consent – Cookie Banner \u0026 Consent Management for GDPR, CCPA \u0026 Google Consent Mode"],"published":"2026-08-15","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-18","vendors":["wplegalpages"]},"summary":"Authenticated users can inject scripts via the regionArray parameter if Google Consent Mode is enabled, leading to stored XSS.","url":"https://insights.sbomify.com/CVE-2026-13360/"}