CVE-2026-8977 MEDIUM

CVE-2026-8977: WP GDPR Cookie Consent <= 1.0.0 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'ninja_gdpr_ajax_actions' AJAX Action

Vendor Techjewel
Product WP GDPR Cookie Consent
Weakness CWE-79 · XSS
Published June 9, 2026
Last update June 9, 2026

CVSS base score

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

CVSS vector

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

What the vulnerability does

01Description

The WP GDPR Cookie Consent plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'ninja_gdpr_ajax_actions' AJAX action in versions up to, and including, 1.0.0. This is due to missing capability and nonce checks on the handleAjaxCalls() function, combined with insufficient input sanitization on the gdprConfig values and missing output escaping in the generateCSS() function which echoes stored configuration values directly into a <style> block rendered on wp_head. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Explanation of Vulnerability in Simple Terms

02Summary

WP GDPR Cookie Consent versions up to 1.0.0 contain a stored cross-site scripting (XSS) vulnerability. An authenticated user with low privileges can inject malicious scripts that execute in other users' browsers, including administrators. The vulnerability affects the plugin's scope across the site, potentially compromising user sessions and data.

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that run in other users' browsers, including admins, to steal sessions or data.

Potential impact on your site

04Site Impact

Authenticated attackers can compromise admin accounts and steal sensitive site data through injected scripts.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege WordPress account (e.g., subscriber or contributor role).

Key dates

06Disclosure timeline

June 9, 2026 CVE published
June 9, 2026 Record updated