Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-45330 medium CVSS 4.9

Information Disclosure in decidim-verifications (CVE-2026-45330)

Summary

Vulnerability in decidim-verifications (CVE-2026-45330). Confidential information can be exposed externally. Exploitable via id_documents. Mitigation: upgrade to 0.32.0 or later.

Original description

The description as published by the source.

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:

  2. 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

  3. 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)

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

Impact

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

Patches

See https://github.com/decidim/decidim/pull/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.

Source: GitHub Security Advisories (Global) 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-45330 has been found in decidim-verifications.
Attackers can target a specific entry point like id_documents over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 4.9/10.
What to do: upgrade decidim-verifications to 0.32.0 or later.
If unsure, ask your IT team or search "decidim-verifications CVE-2026-45330" on the vendor's site.

CVE-2026-45330 (decidim-verifications) — CWE-200 / CVSS v3 4.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: id_documents
Patched: 0.32.0 — apply immediately
Workaround: Disable the "Identity documents" verification
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.

❓ What is the problem

Information disclosure (CWE-200) exists in decidim-verifications. Attackers reach the vulnerable code path via id_documents.

📍 Affected scope

Check the vendor advisory for the affected versions of decidim-verifications. Attack surface: id_documents.

🔥 Severity

Severity: Medium (CVSS 4.9/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.32.0.

🛡️ Workaround

Workaround: Disable the "Identity documents" verification

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'decidim-verifications' . 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

  1. 1
    Identify exposure identify 
    grep -r 'decidim-verifications' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で decidim-verifications を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Disable the "Identity documents" verification

    パッチが適用されるまでの応急処置として、Disable the "Identity documents" verification を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade decidim-verifications to 0.32.0

    ステージング環境で 0.32.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

rubygems decidim-verifications
[{"type":"ECOSYSTEM","events":[{"introduced":"0.32.0.rc1"},{"fixed":"0.32.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details