Wplp Cookie Consent
Monthly
Missing authorization controls in WPLP Cookie Consent WordPress plugin before 4.4.2 allow any subscriber-level authenticated user to invoke privileged AJAX actions without nonce or capability verification. Affected actions expose administrator scan data for reading and deletion, and permit complete overwrite of the plugin's stored configuration by low-privileged users. A publicly available exploit exists per WPScan, though EPSS is 0.13% (3rd percentile), indicating limited observed exploitation activity to date.
Missing authorization on a cookie-scanner AJAX endpoint in the WPLP Cookie Consent WordPress plugin before 4.4.2 allows any authenticated user with subscriber-level access to read the automated scan schedule configured by an administrator. The flaw (CWE-862) stems from the absence of both nonce validation and WordPress capability checks on the AJAX action handler. While impact is limited to information disclosure of scheduling configuration, a publicly available exploit via WPScan and low barrier to exploitation (any registered user) make patching advisable for all affected sites.
Missing authorization in WPLP Cookie Consent WordPress plugin (versions 3.6.5 through before 4.4.2) allows any authenticated user - including low-privilege subscribers - to overwrite the site-wide cookie consent banner configuration shown to all visitors and irreversibly destroy accumulated A/B test result data. The flaw stems from absent WordPress capability and nonce checks on A/B testing action handlers, meaning no admin intent is required. A POC is publicly available via WPScan; no CISA KEV listing exists and EPSS sits at the 3rd percentile, suggesting opportunistic rather than targeted exploitation.
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. A WPScan-published POC is publicly available; no active exploitation is confirmed in CISA KEV.
SQL injection in WPLP Cookie Consent WordPress plugin (versions 3.0.0 through before 4.4.2) allows authenticated administrators to execute arbitrary SQL queries via an unvalidated pagination parameter passed directly into a database query without sanitization. The vendor CVSS includes a scope-change flag (S:C), indicating the injection may permit cross-schema database reads beyond the plugin's own tables. A publicly available proof-of-concept exists via WPScan, though exploitation is gated behind WordPress administrator credentials.
Missing authorization controls in WPLP Cookie Consent WordPress plugin before 4.4.2 allow any subscriber-level authenticated user to invoke privileged AJAX actions without nonce or capability verification. Affected actions expose administrator scan data for reading and deletion, and permit complete overwrite of the plugin's stored configuration by low-privileged users. A publicly available exploit exists per WPScan, though EPSS is 0.13% (3rd percentile), indicating limited observed exploitation activity to date.
Missing authorization on a cookie-scanner AJAX endpoint in the WPLP Cookie Consent WordPress plugin before 4.4.2 allows any authenticated user with subscriber-level access to read the automated scan schedule configured by an administrator. The flaw (CWE-862) stems from the absence of both nonce validation and WordPress capability checks on the AJAX action handler. While impact is limited to information disclosure of scheduling configuration, a publicly available exploit via WPScan and low barrier to exploitation (any registered user) make patching advisable for all affected sites.
Missing authorization in WPLP Cookie Consent WordPress plugin (versions 3.6.5 through before 4.4.2) allows any authenticated user - including low-privilege subscribers - to overwrite the site-wide cookie consent banner configuration shown to all visitors and irreversibly destroy accumulated A/B test result data. The flaw stems from absent WordPress capability and nonce checks on A/B testing action handlers, meaning no admin intent is required. A POC is publicly available via WPScan; no CISA KEV listing exists and EPSS sits at the 3rd percentile, suggesting opportunistic rather than targeted exploitation.
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. A WPScan-published POC is publicly available; no active exploitation is confirmed in CISA KEV.
SQL injection in WPLP Cookie Consent WordPress plugin (versions 3.0.0 through before 4.4.2) allows authenticated administrators to execute arbitrary SQL queries via an unvalidated pagination parameter passed directly into a database query without sanitization. The vendor CVSS includes a scope-change flag (S:C), indicating the injection may permit cross-schema database reads beyond the plugin's own tables. A publicly available proof-of-concept exists via WPScan, though exploitation is gated behind WordPress administrator credentials.