DecidimApplication
CVE-2024-45594
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 · uneditedDecidim is a participatory democracy framework. The meeting embeds feature used in the online or hybrid meetings is subject to potential XSS attack through a malformed URL. This vulnerability is fixed in 0.28.3 and 0.29.0.
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 · moderate confidenceDecidim's meeting embeds feature for online/hybrid meetings is vulnerable to stored XSS through malformed URLs. Attackers can inject malicious scripts via the meeting embed URL parameter that gets rendered without proper sanitization, allowing script execution in the context of other users' browsers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
DecidimApplication
>= 0.28.0, < 0.28.3CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Decidim versionLocate the Decidim version file or gemspec in your deployment (typically in config/initializers/version.rb, Gemfile.lock, or the Decidim gem). Run a command like `grep -r 'Decidim::VERSION' app/` or inspect your Gemfile.lock for the decidim gem version.Affected if The installed version is 0.28.0, 0.28.1, or 0.28.2 (any version >= 0.28.0 but < 0.28.3)
-
Verify meeting module is activeCheck if the Decidim meetings component is enabled in your organization configuration. Look in your database in the `decidim_organizations` table or the component settings in the admin panel to confirm meetings module is present and active.Affected if The meetings component is enabled and accessible to users in your Decidim instance
-
Inspect meeting embed configurationCheck the meeting embeds feature settings. This is typically found in the Decidim admin panel under Components > Meetings > Embeds, or by inspecting the database tables related to meeting configuration (such as `decidim_meetings_meetings` if embed-related columns exist).Affected if Meeting embed functionality is configured and available for online or hybrid meetings
-
Review meeting embed URL handlingTest creating or editing a meeting with a custom embed URL. Access the meeting creation form, locate the embed URL field, and examine how the application handles URL input and display in the meeting show page.Affected if The application accepts custom embed URLs without explicit validation or renders embedded content without proper output encoding
You are affected if your Decidim installation is version 0.28.0 through 0.28.2 and the meetings component with embed functionality is enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scoped0.28.3
Upgrade Decidim to version 0.28.3, 0.29.0, or later to apply the security patch that adds proper URL validation and output encoding in the meeting embeds component.
0.28.3 or 0.29.0
- Review the Decidim upgrade notes for version 0.28.3 or 0.29.0 for any migration requirements
- Back up your current database and application code
- Update the Decidim version in your Gemfile to 0.28.3 (or 0.29.0 for the latest stable)
- Run `bundle install` to update dependencies
- Run any required database migrations
- Redeploy your application
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Decidim
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45594 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-45594 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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