WPLP Cookie Consent <= 4.4.1 - Unauthenticated Arbitrary File Upload via 'upload-logo' REST Endpoint
Strategic Overview
- Status
- Patched in 4.4.2
- Affected Plugin
- WPLP Cookie Consent – Cookie Banner & Consent Management for GDPR, CCPA & Google Consent Mode
- Affected Version
<= 4.4.1- CVSS
- 9.8Critical
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2026-75865
At a glance
CVE-2026-75865 is a critical-severity Unrestricted Upload of File with Dangerous Type vulnerability in the WPLP Cookie Consent WordPress plugin, affecting versions <= 4.4.1. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.4.2; sites on affected versions should update now. Disclosed August 2026, reported by Supakiad S. (m3ez).
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-434: Unrestricted Upload of File with Dangerous Type
WPLP Cookie Consent <= 4.4.1 carries this weakness at saas_upload_logo(), and reaching it takes no account at all. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.
If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For WPLP Cookie Consent the fix is 4.4.2: builds <= 4.4.1 are affected, anything from 4.4.2 onward is not.
Remediation
Update to version 4.4.2, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: WPLP Cookie Consent 4.4.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Login Security
External References
Related records
Other vulnerabilities in WPLP Cookie Consent – Cookie Banner & Consent Management for GDPR, CCPA & Google Consent Mode
- 7.5CVE-2025-11754: Cookie Banner Info Exposure
CVE-2025-11754 - 7.2CVE-2026-13360: Cookie Banner for GDPR / CCPA <= 4.3.5 Stored XSS
CVE-2026-13360 - 7.2CVE-2024-4869: WP Cookie Consent Stored XSS
CVE-2024-4869 - 6.4CVE-2026-73359: WPLP Cookie Consent Stored XSS
CVE-2026-73359 - 6.4CVE-2023-23678: WP Cookie Notice for GDPR CSV Injection
CVE-2023-23678 - 6.3CVE-2022-4974: Freemius SDK <= 2.4.2 Missing Authorization Checks
CVE-2022-4974 - 5.3CVE-2025-66080: Cookie Notice for GDPR Missing Authorization
CVE-2025-66080 - 5.3CVE-2025-14061: Cookie Banner Unauthenticated Arbitrary Post Deletion
CVE-2025-14061
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C