Skip to content

Decidim: Verification admins can access supplied IDs from other organizations

Moderate severity GitHub Reviewed Published Jul 13, 2026 in decidim/decidim • Updated Jul 13, 2026

Package

bundler decidim-verifications (RubyGems)

Affected versions

< 0.30.9
>= 0.31.0.rc1, < 0.31.5
>= 0.32.0.rc1, < 0.32.0

Patched versions

0.30.9
0.31.5
0.32.0

Description

Description

The verification admin mutation flow allows accessing, verifying, and rejecting participants records from another tenant.

Technical description

The verification admin controllers loads pending_authorization_id with a raw Authorization.find(...) and then authorizes the record without checking whether it belongs to current_organization.

Reproduction steps:

  1. An org2 participant uploads their ID:

decidim-verification-01

  1. An admin from another organisation, in this case org1, is able to open the ID from org2 by opening request 35, e.g http://localhost:3001/admin/id_documents/pending_authorizations/35/confirmations/new

decidim-verification-02

  1. The admin then approves this request by looking up the ID in the picture (not shown in this image, but a real ID would expose this)

decidim-verification-03

  1. Now the request has been approved, which can be seen from the org2 participant authorizations page:

decidim-verification-04

Impact

A tenant admin can access, reject or approve another tenant's id_documents requests.

Patches

See decidim/decidim#16666

Workarounds

Disable the "Identity documents" verification

Reference

OWASP A01:2021 Broken Access Control

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.

References

@andreslucena andreslucena published to decidim/decidim Jul 13, 2026
Published to the GitHub Advisory Database Jul 13, 2026
Reviewed Jul 13, 2026
Last updated Jul 13, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(20th percentile)

Weaknesses

Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Learn more on MITRE.

CVE ID

CVE-2026-45330

GHSA ID

GHSA-86fh-w43w-338c

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.