Black Friday60% off BLACKFRIDAY2026
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
medium·Product Based Web Vulnerabilities·Updated Nov 9, 2026

CVE-2026-82186 Scanner

CVE-2026-82186 Scanner - SQL Injection vulnerability in WordPress WPLP Cookie Consent

Est. Time~1 minutes
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
2
Times Used
continuous scan runs
4.4k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
4.1
CVSSmedium
Exploitable remotely over the internet · requires high privileges.
Description

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.

Attack Vector
Network
Privileges Req.
High
User Interaction
None
Affected
WPLP Cookie Consent
AFFECTED< 4.4.2→SAFE ✓≥ 4.4.2
Updated Nov 6, 2026View on NVD →
Detail

WordPress WPLP Cookie Consent is a widely used plugin that serves the purpose of managing cookie consent for compliance with privacy regulations. It becomes an integral part of websites built on the WordPress platform, allowing website administrators to define how they handle cookies and what consent options they display to site visitors. Developed for WordPress, one of the most popular content management systems, this plugin is particularly used by businesses that need to adhere to GDPR and other data protection regulations. With an easy-to-use interface, it enables both technical and non-technical users to configure cookie policies effectively. The plugin is particularly significant for websites that aim to ensure user privacy and comply with legal requirements. Due to its critical role, maintaining security in this plugin is essential for protecting against vulnerabilities.

An SQL Injection vulnerability can be present when user input is not properly sanitized and is used within SQL queries, allowing an attacker to execute arbitrary SQL commands. In the case of the WordPress WPLP Cookie Consent plugin, a pagination parameter is vulnerable to this form of attack. SQL Injection occurs because the input is directly included in the SQL statement. This vulnerability is rated medium due to its dependency on administrator privileges, reducing the potential attack vector. The impact is typically associated with unauthorized data disclosure and could affect the integrity or availability of the database.

From a technical standpoint, the vulnerability in the WordPress WPLP Cookie Consent plugin is found in the way it handles a pagination parameter. This parameter, lacking proper validation, can be manipulated to insert malicious SQL commands into the database query. The vulnerability allows an attacker, who gains access with sufficient privileges, to execute time-based SQL commands leveraging the SQL SLEEP function. Specifically, the vulnerable endpoint is within the admin-ajax.php interface, which handles requests from authenticated users. This makes the vulnerability particularly risky as it lies in the execution path of authorized users with elevated privileges, showcasing a potential weak point in the access control.

Exploiting this vulnerability can lead to several potential effects, including unauthorized access to sensitive data or administrative functionalities of the WordPress site. When successfully executed, malicious users could extract user data, alter existing data, or potentially disrupt database operations. Even though the vulnerability requires administrator-level access, if exploited, it could enable the execution of commands that affect the integrity and availability of data stored within the application. In the worst-case scenario, it could allow a malicious user to gain control of the site or deface it by altering or deleting data.

REFERENCES

Solution Advice
  • Update the WordPress WPLP Cookie Consent plugin to version 4.4.2 or later.
  • Ensure that input validation and parameterized queries are implemented to prevent SQL Injection.
  • Limit database permissions to only what is necessary for the plugin to operate.
  • Regularly audit plugins and components for security updates and apply patches as needed.
  • Employ a Web Application Firewall (WAF) to help detect and block malicious input.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

12,000+ scanners. Free to start. No credit card required.