External risk intelligence

WP Legal Pages Cookie Notice Unrestricted File Upload Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 10.0)

CVE-2026-82970

The vulnerability exists in a WordPress plugin designed to provide cookie consent notices, which are standard components of public-facing websites. As this plugin is intended to be rendered to all visitors of a website, the functionality is commonly deployed in an internet-facing context.

Unrestricted File Upload

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in a WordPress plugin used for managing cookie consent. This issue allows for the upload of malicious files, potentially impacting website integrity and data security. The main concern is confirming the relevance and exposure of this plugin within our digital assets.

  • Allows malicious file uploads.
  • Impacts websites using the plugin.
  • Confirm relevance and exposure.

Attack Path

How an attacker could exploit the issue

An attacker can upload malicious files to a website using the WP Cookie Notice for GDPR, CCPA & ePrivacy Consent plugin, bypassing security measures. This could allow them to execute arbitrary code or take control of the website.

  • No authentication needed for attack.
  • Uploading a malicious file triggers vulnerability.
  • Enables arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to upload malicious files to the affected WordPress plugin. When supported by the advisory, this could lead to the compromise of website data or services.

  • Website data and services at risk.
  • Malicious files could be uploaded.
  • Unauthorized system access or control.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts a WordPress plugin, making website owners and their application support teams the primary stakeholders. The immediate priority is to determine the plugin's presence on internet-facing or critical systems. Once identified, the accountable owner must be located to initiate a risk-based remediation plan.

  • Website owners should own the issue.
  • Verify plugin presence on public-facing systems.
  • Plan remediation with vendor coordination.

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 WP Cookie Notice for GDPR, CCPA & ePrivacy Consent?

This is a WordPress plugin that website administrators install to manage compliance with data privacy laws. It displays the consent banners visitors see when they first arrive at a site, handling the technical requirements for tracking and cookie permissions.

What does CWE-434 mean regarding CVE-2026-82970?

CWE-434 refers to Unrestricted Upload of File with Dangerous Type. In the context of this CVE, it means the plugin fails to properly limit the types of files users can upload. Because this validation is missing, an attacker can upload files that the server might execute as code, rather than just storing them as static data.

How can an attacker trigger this vulnerability?

An attacker triggers this by interacting with the plugin's file upload functionality. Crucially, the vulnerability does not require the attacker to have an existing account or administrative privileges to the WordPress site. Simply uploading a file with a malicious extension or content is sufficient to initiate the attack.

Why does Halo Surface Signal categorize this as internet-facing?

Halo Surface Signal identifies this as internet-facing because the plugin is designed to provide cookie consent notices to all public visitors of a website. Since the plugin's core purpose is to be visible on public pages, it is almost always deployed in a location accessible from the open internet, making it reachable for external attackers.

Do I need to check my WordPress sites for this plugin?

Yes. If you manage WordPress sites, you should confirm if this specific plugin is installed. If it is present, treat it as a priority for your maintenance schedule. Work with your technical team to verify the current version and determine the best path forward to secure the site.

References