EUVD-2026-74710
GHSA-rmf2-688x-24h9
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Frontend page load trigger is network-accessible with no auth or interaction; impact is bounded to integrity of one options-table record with no confidentiality or availability loss.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
5DescriptionCVE.org
The WPLP Cookie Consent WordPress plugin before 4.4.2 does not have any authorisation or CSRF checks when storing visitor consent state, and the code that does so runs on every front-end page load, allowing unauthenticated attackers to overwrite a site-wide option with arbitrary data.
AnalysisAI
Unauthenticated arbitrary option overwrite in WPLP Cookie Consent WordPress plugin before 4.4.2 lets any remote visitor corrupt a site-wide WordPress option with attacker-controlled data. The vulnerable consent-state persistence routine lacks both WordPress capability checks (CWE-862) and CSRF token validation, and it fires unconditionally on every front-end page load - no special request path or trigger required. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | No special conditions are required for exploitation: the vulnerable code path executes on every front-end page load of any WordPress site running WPLP Cookie Consent 3.5.0 through 4.4.1 with the plugin active. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 score of 5.3 (Medium, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) accurately reflects the unconstrained network access and zero-authentication requirement while correctly limiting impact to integrity. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Upgrade WPLP Cookie Consent to version 4.4.2 or later, which introduces proper WordPress capability checks and CSRF nonce validation on the consent-state write routine. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
More in Wplp Cookie Consent
View allMissing authorization controls in WPLP Cookie Consent WordPress plugin before 4.4.2 allow any subscriber-level authentic
Missing authorization on a cookie-scanner AJAX endpoint in the WPLP Cookie Consent WordPress plugin before 4.4.2 allows
Missing authorization in WPLP Cookie Consent WordPress plugin (versions 3.6.5 through before 4.4.2) allows any authentic
SQL injection in WPLP Cookie Consent WordPress plugin (versions 3.0.0 through before 4.4.2) allows authenticated adminis
Same weakness CWE-862 – Missing Authorization
View allShare
External POC / Exploit Code
Leaving vuln.today