Quick answers
- Is CVE-2026-85131 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85131 being exploited in the wild.
- How severe is CVE-2026-85131?
- Medium severity, with a CVSS score of 6.5, published 16 September 2026.
- Which products and versions are affected?
- WPLP Cookie Consent before 4.4.4.
- Is there a fix for CVE-2026-85131?
- A patch was published on 2026-09-14: Fixed in version 4.4.4 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-85131 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-85131?
- 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
This is a CSRF (Cross-Site Request Forgery) vulnerability in the plugin's bulk action processing on administration screens. The vulnerable component fails to perform CSRF token validation (nonce checks) or capability/permission verification, and does not restrict bulk operations to the plugin's own records, allowing attackers to target arbitrary posts and pages. An attacker can exploit this by crafting a malicious request (e.g., embedded in a webpage or email) that a logged-in administrator visits, causing the admin's session to execute unauthorized deletion of content. The vulnerability requires the victim to be logged into WordPress but does not require additional authentication. This has been fixed in version 4.4.4.
Affected products
- WPLP Cookie Consent before 4.4.4
Timeline
- 2026-09-14: disclosed
- 2026-09-14: patched: Fixed in version 4.4.4