# CVE-2026-120540: iubenda | All-in-one Compliance for GDPR / CCPA Cookie Consent + more <= 3.13.6 - Unauthenticated Stored Cross-Site Scripting via Comment Content via IUB-COOKIE-BLOCK Marker

Status: published. Published: 2026-11-07. Updated: 2026-11-07.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- iubenda / iubenda | All-in-one Compliance for GDPR / CCPA Cookie Consent + more: ≥ 0; ≤ 3.13.6 (affected, semver). Source: CNA: Wordfence

## Severity and prioritization

- CVSS 3.1: 7.2 (high); CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N; source: CNA: Wordfence

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-79

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/fc26d5a0-86fc-48b5-af8f-73dd9a7f2b39?source=cve (CNA: Wordfence)

- https://plugins.trac.wordpress.org/browser/iubenda-cookie-law-solution/tags/3.13.5/iubenda_cookie_solution.php#L857 (CNA: Wordfence)

- https://plugins.trac.wordpress.org/browser/iubenda-cookie-law-solution/tags/3.13.5/iubenda-cookie-class/iubenda.class.php#L825 (CNA: Wordfence)

- https://plugins.trac.wordpress.org/browser/iubenda-cookie-law-solution/tags/3.13.5/iubenda-cookie-class/simple_html_dom.php#L471 (CNA: Wordfence)

- https://plugins.trac.wordpress.org/browser/iubenda-cookie-law-solution/tags/3.13.5/iubenda-cookie-class/simple_html_dom.php#L2199 (CNA: Wordfence)

- https://plugins.trac.wordpress.org/browser/iubenda-cookie-law-solution/tags/3.13.5/iubenda-cookie-class/simple_html_dom.php#L2231 (CNA: Wordfence)

- https://plugins.trac.wordpress.org/browser/iubenda-cookie-law-solution/tags/3.13.5/iubenda_cookie_solution.php#L832 (CNA: Wordfence)

- https://plugins.trac.wordpress.org/changeset?reponame=&old=3779727%40iubenda-cookie-law-solution&new=3779727%40iubenda-cookie-law-solution (CNA: Wordfence)

## Provenance

- CNA: Wordfence: https://www.cve.org/CVERecord?id=CVE-2026-120540; retrieved 2026-11-07; source updated 2026-11-07

Revision: 53a187854e7e20747b41d3a7ea04ae01c8c28407446560ac57affbfe293f869d

Canonical: https://y2.dev/cve/CVE-2026-120540

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.