Decidim cross-site scripting (XSS) in the admin panel

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.8 · CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N · score source

EPSS

• CVE-2024-27095: 0.34% estimated exploitation activity in the next 30 days; percentile 27.62 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact The admin panel is subject to potential XSS attach in case the attacker manages to modify some records being uploaded to the server. The attacker is able to change e.g. to <svg onload=alert('XSS') if they know how to craft these requests themselves. And then enter the returned blob ID to the form inputs manually by modifying the edit page source. Patches Available in versions 0.27.6 and 0.28.1. Workarounds Review the user accounts that have access to the admin panel (i.e. general Administrators, and participatory space's Administrators) and remove access to them if they don't need it. References OWASP ASVS v4.0.3-5.1.3

Published by the source

10 Jul 2024, 16:02 UTC

Last modified by the source

31 Jul 2024, 05:02 UTC

Source last checked

26 Oct 2026, 15:48 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-529p-jj47-w3m3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-27095

Advisory: Decidim cross-site scripting (XSS) in the admin panel
IDs: CVE-2024-27095, GHSA-529p-jj47-w3m3
Record: https://patchnext.com/advisories/cve-2024-27095 (revision 1, source checked 26 Oct 2026, 15:48 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: decidim-admin 0.28.1, 0.27.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- RubyGems decidim-admin: affected < 0.27.6; >= 0.28.0.rc1, < 0.28.1; fixed in 0.28.1, 0.27.6

## Suggested inspection (read-only)
- RubyGems decidim-admin: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on decidim-admin.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-529p-jj47-w3m3 (GitHub-reviewed advisory GHSA-529p-jj47-w3m3 lists affected ranges: RubyGems decidim-admin >=0 =0.28.0.rc1 <0.28.1)

Commands are suggestions: review each one before running it.