External risk intelligence

WPLP Cookie Consent WordPress Plugin Arbitrary File Upload Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-75865

The vulnerability affects a WordPress plugin designed for public-facing cookie consent and GDPR compliance, which is intended to be accessible to all internet users visiting the website. This functionality is inherently exposed to the public internet by design.

Unrestricted File Upload

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a critical vulnerability found in a WordPress plugin used for managing cookie consent. The flaw allows unauthenticated attackers to upload malicious files to a website's server, potentially leading to the execution of arbitrary code. The main concern is to confirm if this plugin is in use and assess potential exposure.

  • Unauthenticated file uploads can compromise server security.
  • This plugin is designed for public-facing website functions.
  • Confirm relevance and assess exposure to potential threats.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker can exploit this vulnerability by uploading a malicious file to the affected WordPress site. This is possible due to a flaw in how the WPLP Cookie Consent plugin handles file uploads, specifically within the `saas_upload_logo()` function, and an authorization bypass on its associated REST endpoints. Successful exploitation allows an attacker to upload arbitrary files, potentially leading to remote code execution on the server.

  • Requires no prior authentication.
  • Triggers through a file upload function.
  • Allows arbitrary file upload, risking code execution.

Live Threat

Current exploitation, exposure, and threat context

Unauthenticated attackers could upload arbitrary files to the server through a vulnerable WordPress plugin, potentially leading to remote code execution under specific conditions.

  • Server files could be affected.
  • Arbitrary file uploads may occur.
  • Remote code execution is a possibility.

Operational Fix

Recommended remediation, mitigation, and detection steps

For this WordPress plugin vulnerability, the website owner or application administrator is typically responsible for managing plugin installations and updates. The first practical step is to identify all WordPress sites using the affected plugin, confirm their exposure to the internet, and then determine the business criticality of each instance to prioritize remediation.

  • Confirm plugin ownership and scope.
  • Verify public-facing exposure.
  • Plan coordinated updates.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the WPLP Cookie Consent plugin?

It is a WordPress extension designed to help website administrators manage user privacy requirements, such as GDPR and CCPA compliance. It adds a cookie banner and consent tracking tools to a site, making it a common component for businesses that need to inform visitors about data collection practices directly within the browser.

What does CVE-2026-75865 mean for a website?

This vulnerability is classified as Unrestricted Upload of File with Dangerous Type (CWE-434). It means the plugin fails to check what kind of files are being uploaded to the server. Because the security check is missing, the system could be tricked into accepting malicious files instead of just images or logos, potentially allowing an attacker to run custom code on your web server.

How can an attacker trigger this vulnerability?

An attacker can reach the vulnerable REST endpoints without needing an account or any special permissions on the website. The flaw is triggered by sending a specially crafted request to the plugin's logo upload function. This exploit does not require the attacker to have administrative access or to have previously interacted with the site in any way.

Is my website at risk from this vulnerability?

If you are running an older version of this plugin, you should assume high risk. According to Halo Surface Signal, because this plugin is designed to handle public-facing cookie consent, it is inherently meant to be accessible to everyone on the internet. This design choice means there is a direct, open path for attackers to reach the vulnerable code from the public web.

What steps should I take if I use this plugin?

Start by identifying every WordPress installation in your environment that has this plugin active. Once you have a list of affected sites, verify which are accessible to the public internet. Prioritize these public-facing instances for immediate updates, as they are the most reachable by unauthorized parties.

References