---
id: "CVE-2026-120540"
page: "https://infrastack.ai/live/CVE-2026-120540"
kind: "vulnerability"
aliases: ["CVE-2026-120540"]
title: "iubenda WordPress plugin: stored XSS via comments, up to 3.13.6"
severity: "high"
cvss: 7.2
epss: null
exploited: false
status: "open"
category: "runtime"
products: []
ecosystems: []
tags: ["iubenda", "runtime", "self-hosted", "wordpress"]
not_affected_if: ["comments-disabled", "newer-version", "plugin-not-installed"]
published_at: "2026-11-07T03:17:03+00:00"
first_seen_at: "2026-11-07T03:45:35+00:00"
updated_at: "2026-11-07T03:47:45+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-120540", "first_seen_at": "2026-11-07T03:45:35+00:00"}]
exploit_sources: []
---

# iubenda WordPress plugin: stored XSS via comments, up to 3.13.6

Link for people: https://infrastack.ai/live/CVE-2026-120540 (this .md is for agents)

The iubenda cookie consent WordPress plugin up to and including 3.13.6 re-parses HTML in comments, letting a crafted payload escape an attribute and inject script. An unauthenticated attacker can get script to run in visitors' browsers once an administrator approves the first comment.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed iubenda plugin version in the WordPress admin plugin list or `wp plugin get iubenda --field=version`
- Confirm whether the site accepts comments and whether comments are moderated before first approval

## Fix

- iubenda plugin: move to a version later than `3.13.6` (the sources do not name the fixed release)

## Timeline

- 2026-11-07T03:45:35+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-120540

## From the sources

The iubenda | All-in-one Compliance for GDPR / CCPA Cookie Consent + more plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 3.13.6. This is due to the way iubendaParser::parse_comments() re-processes HTML inside IUB-COOKIE-BLOCK markers through the bundled simple_html_dom parser after WordPress has already KSES-filtered the saved comment: simple_html_dom's remove_noise() stores <code> bodies under a deterministic key ('___noise___ 1000') and restore_noise() later substitutes any matching substring back into attribute values WITHOUT re-escaping, allowing a quote-breaking payload stashed in an allowed <code> element to be injected into an allowed <abbr title="___noise___ 1000"> attribute at render time. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page, after an administrator approves the first (otherwise moderated) comment under WordPress's default comment_previously_approved setting.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_