HomeWordPress vulnerabilitiesWPLP Cookie Consent
WPLP Cookie Consent vulnerabilities
WPLP Cookie Consent has 23 known vulnerabilities in this database. The most recent published record is dated 6 Oct 2026.
- Known vulnerabilities
- 23
- Active installs
- 9,000+
- Latest version
- 4.4.6
- Last updated
- 28 Sep 2026
- Most recent
- 6 Oct 2026
No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-42636 | High 7.1 | Up to 4.4.6 | No fixed version yet | 1 d ago |
| Cross-site scripting (XSS) CVE-2026-85130 | High 8.8 | Before 4.4.4 | Fixed in 4.4.4 | 17 Sep 2026 |
| Cross-site request forgery (CSRF) CVE-2026-85131 | Medium 6.5 | Before 4.4.4 | Fixed in 4.4.4 | 16 Sep 2026 |
| Cross-site scripting (XSS) CVE-2026-14989 | High 7.2 | Up to 4.4.1 | Fixed in a later version (latest 4.4.6) | 9 Sep 2026 |
| Broken access control CVE-2026-85132 | Medium 4.3 | Before 4.4.2 | Fixed in 4.4.2 | 9 Sep 2026 |
| Broken access control CVE-2026-85133 | Medium 5.4 | Before 4.4.2 | Fixed in 4.4.2 | 9 Sep 2026 |
| Cross-site request forgery (CSRF) CVE-2026-82184 | Medium 5.3 | Before 4.4.2 | Fixed in 4.4.2 | 9 Sep 2026 |
| Broken access control CVE-2026-82185 | Medium 4.3 | Before 4.4.2 | Fixed in 4.4.2 | 9 Sep 2026 |
| SQL injection CVE-2026-82186 | Medium 4.1 | Before 4.4.2 | Fixed in 4.4.2 | 4 Sep 2026 |
| Remote code execution CVE-2026-75865 | Critical 9.8 | Up to 4.4.1 | Fixed in a later version (latest 4.4.6) | 1 Sep 2026 |
| Cross-site scripting (XSS) CVE-2026-13360 | High 7.2 | Up to 4.3.5 | Fixed in a later version (latest 4.4.6) | 15 Aug 2026 |
| Cross-site request forgery (CSRF) CVE-2026-15136 | Medium 4.3 | Up to 4.3.7 | Fixed in a later version (latest 4.4.6) | 28 Jul 2026 |
| SQL injection CVE-2026-14475 | Medium 4.9 | Up to 4.3.6 | Fixed in a later version (latest 4.4.6) | 10 Jul 2026 |
| Broken access control CVE-2026-12955 | Medium 4.3 | Up to 4.3.6 | Fixed in a later version (latest 4.4.6) | 10 Jul 2026 |
| SQL injection CVE-2026-12920 | Medium 4.9 | Up to 4.3.5 | Fixed in a later version (latest 4.4.6) | 3 Jul 2026 |
| Broken access control CVE-2025-11754 | High 7.5 | Up to 4.1.2 | Fixed in a later version (latest 4.4.6) | 19 Feb 2026 |
| Broken access control CVE-2025-14061 | Medium 5.3 | Up to 4.0.7 | Fixed in a later version (latest 4.4.6) | 17 Dec 2025 |
| Cross-site request forgery (CSRF) CVE-2024-8286 | Medium 6.5 | Before 2.6.1 | Fixed in 2.6.1 | 15 May 2025 |
| Cross-site scripting (XSS) CVE-2024-8397 | Medium 5.4 | Before 2.61 | Fixed in 2.61 | 15 May 2025 |
| Broken access control CVE-2024-11724 | Medium 4.3 | Before 3.6.6 | Fixed in 3.6.6 | 12 Dec 2024 |
| Cross-site scripting (XSS) CVE-2024-4869 | High 7.2 | Before 3.3.0 | Fixed in 3.3.0 | 26 Jun 2024 |
| Broken access control CVE-2024-3599 | Medium 5.3 | Before 3.1.0 | Fixed in 3.1.0 | 2 May 2024 |
| Cross-site scripting (XSS) CVE-2020-20633 | Medium 5.4 | Up to 1.8.2 | Fixed in a later version (latest 4.4.6) | 21 Aug 2020 |
Read the published descriptions
- CVE-2026-42636, 6 Oct 2026
- Unauthenticated Cross Site Scripting (XSS) in WP Cookie Notice for GDPR, CCPA & ePrivacy Consent <= 4.4.6 versions. CVE record
- CVE-2026-85130, 17 Sep 2026
- The WPLP Cookie Consent WordPress plugin before 4.4.4 does not escape a value submitted through a public endpoint for the JavaScript context it is later output in on an administrative screen, allowing unauthenticated users to run arbitrary JavaScript in the session of an administrator who interacts with the logged entry. Only multisite installations are affected. CVE record
- CVE-2026-85131, 16 Sep 2026
- 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. CVE record
- CVE-2026-14989, 9 Sep 2026
- The Cookie Banner for GDPR / CCPA - WPLP Cookie Consent plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'wpl_user_preference' parameter in all versions up to, and including, 4.4.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The consent-logging AJAX endpoint is registered for unauthenticated users and its required nonce (wpl_consent_logging_nonce) is publicly emitted via wp_localize_script on the frontend, meaning any unauthenticated site visitor can plant a payload without any prior authentication or privileged access. CVE record
- CVE-2026-85132, 9 Sep 2026
- The WPLP Cookie Consent WordPress plugin before 4.4.2 does not perform nonce or capability checks on one of its cookie scanner AJAX actions, allowing any authenticated user, such as a subscriber, to read back the automated scan schedule the administrator configured. CVE record
- CVE-2026-85133, 9 Sep 2026
- The WPLP Cookie Consent WordPress plugin before 4.4.2 does not perform nonce or capability checks on several of its settings AJAX actions, allowing any authenticated user, such as a subscriber, to read and destroy scan data belonging to the administrator and to overwrite the WPLP Cookie Consent WordPress plugin before 4.4.2's stored configuration. CVE record
- CVE-2026-82184, 9 Sep 2026
- 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. CVE record
- CVE-2026-82185, 9 Sep 2026
- The WPLP Cookie Consent WordPress plugin before 4.4.2 does not have capability or nonce checks on some of its A/B testing actions, allowing any authenticated user, such as a subscriber, to overwrite the cookie banner configuration shown to every visitor and to irreversibly reset the stored A/B test results. CVE record
- CVE-2026-82186, 4 Sep 2026
- The WPLP Cookie Consent WordPress plugin before 4.4.2 does not properly validate a pagination parameter before using it in a SQL query, allowing users with administrator privileges to perform SQL injection attacks. CVE record
- CVE-2026-75865, 1 Sep 2026
- The WPLP Cookie Consent - Cookie Banner & Consent Management for GDPR, CCPA & Google Consent Mode plugin for WordPress is vulnerable to arbitrary file upload due to missing file type validation in the saas_upload_logo() function combined with an authorization bypass on the WPLP connector REST endpoints in all versions up to, and including, 4.4.1. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible. CVE record
- CVE-2026-13360, 15 Aug 2026
- The Cookie Banner for GDPR / CCPA - WPLP Cookie Consent plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'regionArray' parameter in all versions up to, and including, 4.3.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires that the site administrator has enabled the 'Support Google Consent Mode (GCM)' setting, which is disabled by default. Additionally, the AJAX handler performs no nonce or capability check, allowing any authenticated user including those with Subscriber-level access to overwrite the affected plugin setting. CVE record
- CVE-2026-15136, 28 Jul 2026
- The Cookie Banner for GDPR / CCPA - WPLP Cookie Consent plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.3.7. This is due to missing or incorrect nonce validation on the process_bulk_action function. This makes it possible for unauthenticated attackers to permanently delete or forcibly resolve arbitrary GDPR data request records stored in the wpl_data_req table via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
- CVE-2026-14475, 10 Jul 2026
- The Cookie Banner for GDPR / CCPA - WPLP Cookie Consent plugin for WordPress is vulnerable to generic SQL Injection via the 'scan_id' parameter in all versions up to, and including, 4.3.6 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. CVE record
- CVE-2026-12955, 10 Jul 2026
- The GDPR Cookie Consent plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check and missing nonce verification on the gdpr_cookie_consent_ajax_save_schedule_scan() function (the wp_ajax_gcc_save_schedule_scan AJAX action) in versions up to, and including, 4.3.6. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify the plugin's cookie scan schedule configuration stored in the gdpr_scan_schedule_data option, which is an administrative function intended to be limited to users with the manage_options capability. CVE record
- CVE-2026-12920, 3 Jul 2026
- The Cookie Banner for GDPR / CCPA - WPLP Cookie Consent plugin for WordPress is vulnerable to generic SQL Injection via the 's' parameter in all versions up to, and including, 4.3.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. CVE record
- CVE-2025-11754, 19 Feb 2026
- The GDPR Cookie Consent plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'gdpr/v1/settings' REST API endpoint in all versions up to, and including, 4.1.2. This makes it possible for unauthenticated attackers to retrieve sensitive plugin settings including API tokens, email addresses, account IDs, and site keys. CVE record
- CVE-2025-14061, 17 Dec 2025
- The Cookie Banner, Cookie Consent, Consent Log, Cookie Scanner, Script Blocker (for GDPR, CCPA & ePrivacy) : WP Cookie Consent plugin for WordPress is vulnerable to unauthorized data modification due to a missing capability check on the gdpr_delete_policy_data function in all versions up to, and including, 4.0.7. This makes it possible for unauthenticated attackers to permanently delete arbitrary posts, pages, attachments, and other post types by ID. CVE record
- CVE-2024-8286, 15 May 2025
- The webtoffee-gdpr-cookie-consent WordPress plugin before 2.6.1 does not have CSRF checks in some bulk actions, which could allow attackers to make logged in admins perform unwanted actions, such as deleting visit logs via CSRF attacks CVE record
- CVE-2024-8397, 15 May 2025
- The webtoffee-gdpr-cookie-consent WordPress plugin before 2.6.1 does not properly sanitize and escape the IP headers when logging them, allowing visitors to conduct Stored Cross-Site Scripting attacks. The payload gets triggered when an admin visits the 'Consent report' page and the malicious script is executed in the admin context. CVE record
- CVE-2024-11724, 12 Dec 2024
- The Cookie Consent for WP - Cookie Consent, Consent Log, Cookie Scanner, Script Blocker (for GDPR, CCPA & ePrivacy) plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the wpl_script_save AJAX action in all versions up to, and including, 3.6.5. This makes it possible for authenticated attackers, with Subscriber-level access and above, to whitelist scripts. CVE record
- CVE-2024-4869, 26 Jun 2024
- The WP Cookie Consent ( for GDPR, CCPA & ePrivacy ) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘Client-IP’ header in all versions up to, and including, 3.2.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2024-3599, 2 May 2024
- The WP Cookie Consent ( for GDPR, CCPA & ePrivacy ) plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the gdpr_policy_process_delete() function in all versions up to, and including, 3.0.2. This makes it possible for unauthenticated attackers to delete arbitrary posts. CVE record
- CVE-2020-20633, 21 Aug 2020
- ajax_policy_generator in admin/modules/cli-policy-generator/classes/class-policy-generator-ajax.php in GDPR Cookie Consent (cookie-law-info) 1.8.2 and below plugin for WordPress, allows authenticated stored XSS and privilege escalation. CVE record
What to do if you run WPLP Cookie Consent
If you run WPLP Cookie Consent, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new WPLP Cookie Consent vulnerabilities
Free. We email you when a new vulnerability is published for WPLP Cookie Consent, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.