Skip to content
Fencer Intel
critical 9.1

CVE-2023-36465 json

Decidim has broken access control in templates

published 3y ago modified 2mo ago also GHSA-639h-86hw-qcjq , EUVD-2023-2663

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits
0
none known

Summary

Decidim is a participatory democracy framework, written in Ruby on Rails, originally developed for the Barcelona City government online and offline participation website. The `templates` module doesn't enforce the correct permissions, allowing any logged-in user to access to this functionality in the administration panel. An attacker could use this vulnerability to change, create or delete templates of surveys. This issue has been patched in version 0.26.8 and 0.27.4.

Patch / fix

  • rubygems decidim 0.26.8, 0.27.4
  • rubygems decidim-templates 0.26.8, 0.27.4
  • decidim decidim 0.26.8, 0.27.4

Is CVE-2023-36465 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

0.67% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-14).

CVSS scores

assigned by version score vector
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:L
NVD 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
GitHub 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L

Affected packages

ecosystem package affected fixed in
rubygems decidim
>=0.23.2, <0.26.8
>=0.27.0, <0.27.4
0.26.8
0.27.4
rubygems decidim-templates
>=0.23.2, <0.26.8
>=0.27.0, <0.27.4
0.26.8
0.27.4

Affected products

  • decidim decidim

Classification

Weakness
  • CWE-284 Improper Access Control
  • CWE-732 Incorrect Permission Assignment for Critical Resource

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.