Quick answers
- Is CVE-2026-45572 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45572 being exploited in the wild.
- How severe is CVE-2026-45572?
- Medium severity, with a CVSS score of 4.8, published 6 August 2026.
- Which products and versions are affected?
- decidim-core (RubyGems) ECOSYSTEM:introduced=0,fixed=0.30.9.
- Is there a fix for CVE-2026-45572?
- Yes. decidim-core (RubyGems): upgrade to 0.30.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45572 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-45572?
- Check whether you run decidim-core (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- decidim-core (RubyGems): upgrade to 0.30.9 or later
bundle update decidim-core
Technical details
A stored cross-site scripting (XSS) vulnerability exists in Decidim's content block system. The root cause is the use of the `.html_safe` method in `Decidim::ContentBlocks::HtmlCell#html_content` (and related cells like SummaryCell and SectionCell) which renders admin-supplied HTML without a sanitization boundary. An attacker with administrative privileges to edit landing pages can persist arbitrary JavaScript that executes in the context of any user visiting the affected page. The vulnerability has been addressed by replacing `.html_safe` with the `decidim_sanitize_editor_admin` helper to properly neutralize unsafe tags and attributes. Patches are available in versions 0.30.9, 0.31.5, and 0.32.0.
Affected products
- Decidim decidim-core < 0.30.9, >= 0.31.0.rc1, < 0.31.5, >= 0.32.0.rc1, < 0.32.0
Identifiers
- CVE-2026-45572
- GHSA-533c-2vh9-4r86
Timeline
- 2026-03-23: other: Pull request with fix submitted
- 2026-05-07: patched: Fix merged into develop branch
- 2026-07-13: advisory: GitHub Advisory published