dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-8977

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WP GDPR Cookie Consent plugin for WordPress versions up to 1.0.0 contains a stored XSS vulnerability. The handleAjaxCalls() AJAX function lacks capability and nonce checks, allowing authenticated subscribers to modify gdprConfig values via the ninja_gdpr_ajax_actions action. These values are then echoed without output escaping in the generateCSS() function directly into a <style> block rendered on wp_head, causing stored scripts to execute on page access.

MitigationAdd capability checks and nonce verification to handleAjaxCalls(), sanitize gdprConfig input before storage, and escape output in generateCSS() before echoing into the style block. Update to the latest patched version when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify plugin installation and version
    Check if the WP GDPR Cookie Consent plugin is installed by looking in wp-content/plugins/ for a folder containing 'gdpr' or 'cookie-consent', then open the main plugin PHP file and look for the 'Version:' header comment to determine the installed version number
    Affected if The plugin is installed and the version falls within any vulnerable range or cannot be determined
  2. Verify plugin activation status
    Check the WordPress database wp_options table for the active_plugins option, or use WP Admin > Plugins to confirm the GDPR Cookie Consent plugin is active
    Affected if The plugin is installed and currently activated on the WordPress site
  3. Inspect stored gdprConfig values for suspicious content
    Query the wp_options table for rows where option_name contains 'gdpr' or 'cookie' - examine any gdprConfig or similar configuration values for unescaped HTML, JavaScript, or CSS-like content such as <script>, javascript:, or style= attributes that could indicate stored XSS
    Affected if The database contains gdprConfig values with unescaped HTML, script tags, or malicious CSS injections
  4. Review generateCSS() function output handling
    Locate the generateCSS() function in the plugin files and examine how it handles gdprConfig values - check if output is properly escaped using functions like esc_html(), esc_attr(), or wp_strip_all_tags() before rendering into the <style> block
    Affected if The generateCSS() function outputs gdprConfig values without proper escaping or sanitization

A user is affected if the WP GDPR Cookie Consent plugin is installed and active with a vulnerable version where gdprConfig values can be stored and output without escaping in the generateCSS() function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add capability checks and nonce verification to handleAjaxCalls(), sanitize gdprConfig input before storage, and escape output in generateCSS() before echoing into the style block. Update to the latest patched version when available.

Recommended fix Moderate confidence

Latest version of WP GDPR Cookie Consent plugin (verify 1.0.1 or higher on wordpress.org)

  1. 1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
  2. 2. Locate the WP GDPR Cookie Consent plugin in the list
  3. 3. Check the current installed version number to confirm it is 1.0.0 or below
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, manually download the latest version from wordpress.org/plugins/wp-gdpr-cookie-consent/ and upload via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is active and functioning correctly
  7. 7. Clear any caching plugins or server-side caches to ensure the patched code is served

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8977 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8977 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data