VulnerabilityPublished 13 Jul 2026

CVE-2026-45330: Decidim · Veriﬁcation admins can access supplied IDs from other organizations

Affects decidim-verificationsSource GCVE Database

Compare

Not known to be exploited · CVSS 4.9 Medium : upgrade to 0.30.9 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

4.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.30.9, 0.31.5, 0.32.0

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade decidim-verifications to 0.30.9; decidim-verifications to 0.31.5; decidim-verifications to 0.32.0.

Affected software

Product	Affected	Fixed in
RubyGemsdecidim-verifications	Affected <0.30.9	Fixed in 0.30.9
RubyGemsdecidim-verifications	Affected >=0.31.0.rc1 <0.31.5	Fixed in 0.31.5
RubyGemsdecidim-verifications	Affected >=0.32.0.rc1 <0.32.0	Fixed in 0.32.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available as referenced in the Decidim GitHub pull request https://github.com/decidim/decidim/pull/16666. Users should upgrade to version 0.30.9 or later where this issue is fixed. As a temporary workaround, disabling the "Identity documents" verification feature prevents cross-tenant access. No other mitigation steps are indicated by the vendor advisory.

Description

A vulnerability in Decidim verification admin functionality allows an admin from one organization to access, approve, or reject identity document verification requests belonging to participants of other organizations. This occurs because the system does not verify that the pending authorization record belongs to the current organization before allowing access and actions. The issue affects Decidim versions prior to 0.30.9. A patch is available as referenced in the Decidim GitHub pull request. As a workaround, disabling the "Identity documents" verification feature can prevent exploitation.

Impact

An attacker with verification admin privileges in one organization can view sensitive identity documents submitted by participants of other organizations, and can approve or reject those verification requests. This leads to unauthorized disclosure of personally identifiable information and unauthorized modification of verification status across tenant boundaries.

Summary

The verification admin mutation flow in Decidim loads pending authorization records using a raw database query without verifying organizational ownership. This allows a verification admin from one tenant to access and manage identity document verification requests from another tenant. The vulnerability is classified as broken access control (CWE-200). It affects Decidim versions before 0.30.9. The issue was discovered during a security audit and a patch is available in the Decidim repository. The vulnerability has moderate severity with a CVSS 3.1 vector indicating network attack vector, low attack complexity, high privileges required, no user interaction, unchanged scope, high confidentiality impact, no integrity or availability impact.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jul 2026, 10:02 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats