CVE-2026-1084 MEDIUM

CVE-2026-1084: Cookie consent for developers <= 1.7.1 - Authenticated (Administrator+) Stored Cross-Site Scripting via Multiple Settings Fields

Vendor Lovor
Product Cookie consent for developers
Weakness CWE-79 · XSS
Published January 24, 2026
Last update April 8, 2026

CVSS base score

4.4/10
Attack vector Network
Attack complexity High
Privileges required High
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

The Cookie consent for developers plugin for WordPress is vulnerable to Stored Cross-Site Scripting via multiple settings fields in all versions up to, and including, 1.7.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

Explanation of Vulnerability in Simple Terms

02Summary

The Cookie Consent for Developers plugin contains a cross-site scripting (XSS) vulnerability in versions up to 1.7.1. An authenticated administrator with high privileges can inject malicious scripts that execute in other users' browsers, potentially affecting site visitors and staff. The vulnerability requires specific attack conditions but can alter page content or steal session data.

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that run in other users' browsers to steal data or alter page content.

Potential impact on your site

04Site Impact

A malicious admin can inject scripts affecting other users; if compromised, the plugin poses a risk to visitor and staff sessions.

Conditions required to exploit

05Prerequisites

Attacker must have high-level admin privileges and the site's scope must be affected (Scope: Changed).

Key dates

06Disclosure timeline

January 24, 2026 CVE published
April 8, 2026 Record updated