Quick answers
- Is CVE-2026-13360 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-13360 being exploited in the wild.
- How severe is CVE-2026-13360?
- High severity, with a CVSS score of 7.2, published 15 August 2026.
- Which products and versions are affected?
- WPLP Cookie Consent up to and including 4.3.5.
- Is there a fix for CVE-2026-13360?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-13360 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-13360?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a stored cross-site scripting (XSS) flaw in the 'regionArray' parameter due to insufficient input sanitization and output escaping. The AJAX handler lacks nonce and capability checks, allowing any authenticated user—including those with minimal Subscriber-level permissions—to inject and persist malicious JavaScript. Exploitation requires that the site administrator has enabled the 'Support Google Consent Mode (GCM)' setting, which is off by default. Once injected, the malicious script executes in the browsers of all users who visit pages containing the affected plugin setting.
Affected products
- WPLP Cookie Consent up to and including 4.3.5
Timeline
- 2026-08-15: disclosed