CVE-2026-40870 | decidim up to 0.30.4/0.31.0 Setting /api Decidim::Apiauth commentable authorization (GHSA-ghmh-q25g-gxxx)
VulDBArchived Apr 22, 2026✓ Full text saved
A vulnerability identified as problematic has been detected in decidim up to 0.30.4/0.31.0 . Affected is the function Decidim::Apiauth of the file /api of the component Setting Handler . The manipulation of the argument commentable leads to missing authorization. This vulnerability is uniquely identified as CVE-2026-40870 . The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-358578 · CVE-2026-40870 · GHSA-GHMH-Q25G-GXXX
DECIDIM UP TO 0.30.4/0.31.0 SETTING /API DECIDIM::APIAUTH COMMENTABLE AUTHORIZATION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
6.3 $0-$5k 2.04+
Summaryinfo
A vulnerability labeled as problematic has been found in decidim up to 0.30.4/0.31.0. Affected by this vulnerability is the function Decidim::Apiauth of the file /api of the component Setting Handler. The manipulation of the argument commentable results in authorization. This vulnerability was named CVE-2026-40870. The attack may be performed from remote. There is no available exploit. The affected component should be upgraded.
Detailsinfo
A vulnerability classified as problematic has been found in decidim up to 0.30.4/0.31.0. Affected is the function Decidim::Apiauth of the file /api of the component Setting Handler. The manipulation of the argument commentable with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality. CVE summarizes:
Decidim is a participatory democracy framework. Starting in version 0.0.1 and prior to versions 0.30.5 and 0.31.1, the root level `commentable` field in the API allows access to all commentable resources within the platform, without any permission checks. All Decidim instances are impacted that have not secured the `/api` endpoint. The `/api` endpoint is publicly available with the default configuration. Versions 0.30.5 and 0.31.1 fix the issue. As a workaround, limit the scope to only authenticated users by limiting access to the `/api` endpoint. This would require custom code or installing the 3rd party module `Decidim::Apiauth`. With custom code, the `/api` endpoint can be limited to only authenticated users. The same configuration can be also used without the `allow` statements to disable all traffic to the the `/api` endpoint. When considering a workaround and the seriousness of the vulnerability, please consider the nature of the platform. If the platform is primarily serving public data, this vulnerability is not serious by its nature. If the platform is protecting some resources, e.g. inside private participation spaces, the vulnerability may expose some data to the attacker that is not meant public. For those who have enabled the organization setting "Force users to authenticate before access organization", the scope of this vulnerability is limited to the users who are allowed to log in to the Decidim platform. This setting was introduced in version 0.19.0 and it was applied to the `/api` endpoint in version 0.22.0.
The advisory is available at github.com. This vulnerability is traded as CVE-2026-40870 since 04/15/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit.
Upgrading eliminates this vulnerability.
Productinfo
Name
decidim
Version
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
0.10
0.11
0.12
0.13
0.14
0.15
0.16
0.17
0.18
0.19
0.20
0.21
0.22
0.23
0.24
0.25
0.26
0.27
0.28
0.29
0.30
0.30.0
0.30.1
0.30.2
0.30.3
0.30.4
0.31.0
Website
Product: https://github.com/decidim/decidim/
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 6.4
VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (GitHub_M): 🔒
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Authorization
CWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Timelineinfo
04/15/2026 CVE reserved
04/21/2026 +6 days Advisory disclosed
04/21/2026 +0 days VulDB entry created
04/21/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: GHSA-ghmh-q25g-gxxx
Status: Confirmed
CVE: CVE-2026-40870 (🔒)
GCVE (CVE): GCVE-0-2026-40870
GCVE (VulDB): GCVE-100-358578
Entryinfo
Created: 04/21/2026 22:32
Changes: 04/21/2026 22:32 (65)
Complete: 🔍
Cache ID: 99:A07:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸