Cross-Site Scripting (XSS) in decidim-elections (CVE-2026-44282)
Summary
Cross-site scripting in decidim-elections (CVE-2026-44282). Risk of unauthorized operations or information disclosure. Exploitable via question.body. Mitigation: upgrade to 0.32.0 or later.
Original description
The description as published by the source.
Description
A low-privilege process-scoped admin who can manage elections can store arbitrary HTML in the question statement/body without sanitization, and the public elections UI renders that value unsafely.
Technical description
This stored XSS appears because election question titles are rendered as trusted HTML instead of sanitized text. The election question editor stores question.body as a normal translatable string, and the public helper question_title returns that value with html_safe and no sanitization boundary, so any user who can edit election questions can persist markup or script-bearing payloads that later render on public election pages.
Impact
A low-privilege process-scoped admin or other election editor with question-management rights can persist JavaScript that executes in visitor's browsers on public election pages and voting booth screens.
Patches
See https://github.com/decidim/decidim/pull/16659
Workarounds
Developers should review their implementation's administrator accesses and not give access to untrustworthy users
Resources
OWASP XSS Injection
Credits
This issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44282 has been found in decidim-elections.
Attackers can target a specific entry point like question.body over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.8/10.
What to do: upgrade decidim-elections to 0.32.0 or later.
If unsure, ask your IT team or search "decidim-elections CVE-2026-44282" on the vendor's site.
CVE-2026-44282 (decidim-elections) — CWE-79 / CVSS v3 4.8
Attack vector: remote (network-reachable)
Attack surface: question.body / question_title / html_safe
Patched: 0.32.0 — apply immediately
Workaround: Developers should review their implementation's administrator accesses and not give access to untrustworthy users
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in decidim-elections. Attackers reach the vulnerable code path via question.body.
Check the vendor advisory for the affected versions of decidim-elections. Attack surface: question.body / question_title / html_safe.
Severity: Medium (CVSS 4.8/10). Risk of unauthorized operations or information disclosure.
Update to 0.32.0.
Workaround: Developers should review their implementation's administrator accesses and not give access to untrustworthy users
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'decidim-elections' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'decidim-elections' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
decidim-electionsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Developers should review their implementation's administrator accesses and not give access to untrustworthy usersパッチが適用されるまでの応急処置として、Developers should review their implementation's administrator accesses and not give access to untrustworthy users を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade decidim-elections to 0.32.0ステージング環境で 0.32.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。