Cross-Site Request Forgery (CSRF) in WPLP Cookie Consent (WordPress plugin) (CVE-2026-85131)
Summary
Vulnerability in WPLP Cookie Consent (WordPress plugin) (CVE-2026-85131). Data can be tampered with by attackers.
Original description
The description as published by the source.
The WPLP Cookie Consent WordPress plugin before 4.4.4 does not perform CSRF or capability checks when processing bulk actions on its administration screens, and does not restrict the targeted items to its own records, allowing attackers to make a logged in admin permanently delete arbitrary posts and pages via a crafted request.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-85131 has been found in WPLP Cookie Consent (WordPress plugin).
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WPLP Cookie Consent (WordPress plugin) CVE-2026-85131" on the vendor's site.
CVE-2026-85131 (WPLP Cookie Consent (WordPress plugin)) — CWE-352 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
CSRF (CWE-352) exists in WPLP Cookie Consent (WordPress plugin).
Check the vendor advisory for the affected versions of WPLP Cookie Consent (WordPress plugin).
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで WPLP Cookie Consent (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web contact@wpscan.com
- web nvd.nist.gov
- web wpscan.com
- web github.com