decidim-verifications

Description

A participant manager can access and modify the CSV census record admin forms.

Technical description

The CSV census admin record-management surface under /admin/csv_census/census_logs does not enforce admin-only authorization before rendering or mutating Decidim::Verifications::CsvDatum.

A participant manager (which can only manage participants) can therefore open the admin forms, create or update census rows, and delete rows directly.

Reproduction steps:

1. Sign in a participant admin and open http://localhost:3000/admin/csv_census/census_logs/new_record in the browser. Confirm the create form loads even though the session is not a full admin.

Note that normal participant accounts were not able to access the CSV census records which is good.

Impact

Any participant admin can create, alter, or remove CSV census rows, which can corrupt verification data relied on by authorization workflows.

Patches

See https://github.com/decidim/decidim/pull/16674 and https://github.com/decidim/decidim/pull/16703

Workarounds

Disable Organization Census verification method

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.

Description

Scanned identity-document images provided by participants and shown in the verification admin workflow are exposed through signed /rails/active_storage/disk/ URLs that can be fetched without any authenticated session.

Anyone who obtains one of those URLs can retrieve the document until the signature expires.

Technical description

This issue comes from the verification admin UI exposing scanned documents through reusable Active Storage disk links. Verification-document images are rendered with variant_url(...), which produces signed /rails/active_storage/disk/... links instead of routing the file through an authorization-checking controller. Because Decidim configures Active Storage service URLs to remain valid for seven days, the URL itself becomes the credential for that period.

The affected files are verification_attachment blobs on Decidim::Authorization, and the admin review pages embed those signed URLs directly into the HTML for pending and confirmation views.

Reproduction steps:

1. Create a fresh verification document as a normal user. 1.1. Open http://localhost:3001/users/sign_in. 1.2. Open http://localhost:3001/id_documents/authorizations/new. 1.3. Submit an id_documents verification request with an image attachment.

2. Open the admin review page that renders the attachment. 2.1. Sign out. 2.2. Sign back in as admin@example.org. 2.3. Try http://localhost:3001/admin/id_documents.

3. Harvest the signed Active Storage URL. 3.1. Open DevTools Network before loading the review page. 3.2. Reload the page. 3.3. Copy one request URL matching http://localhost:3001/rails/active_storage/disk/<SIGNED_TOKEN>/<FILENAME>.

4. Replay the file URL without any Decidim session. 4.1. Open a private window or a second browser where you are not signed in to Decidim. 4.2. Paste the exact copied /rails/active_storage/disk/... URL. 4.3. Confirm the verification image still loads.

Impact

• This only applies to Organizations using the "Identity documents" verification
• Any party that obtains one of these URLs can download the underlying scanned identity document for the lifetime of the signed link without needing to authenticate as the reviewing admin.
• In the reproduced case, that replay window was about seven days, which is long enough for routine leakage channels such as copied links, screenshots, logs, browser history, and support workflows to become realistic exfiltration paths.
• This raises the risk of leakage through browser history, screenshots, copy-paste, support tickets, logs, analytics tooling, malicious browser extensions, or any other channel that captures full URLs.
• Because the affected files are identity-verification documents, the exposed data can include highly sensitive personal information.

Patches

See https://github.com/decidim/decidim/pull/16680

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.

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.

Description

A participant manager can access and modify the CSV census record admin forms.

Technical description

The CSV census admin record-management surface under /admin/csv_census/census_logs does not enforce admin-only authorization before rendering or mutating Decidim::Verifications::CsvDatum.

A participant manager (which can only manage participants) can therefore open the admin forms, create or update census rows, and delete rows directly.

Reproduction steps:

1. Sign in a participant admin and open http://localhost:3000/admin/csv_census/census_logs/new_record in the browser. Confirm the create form loads even though the session is not a full admin.

Note that normal participant accounts were not able to access the CSV census records which is good.

Impact

Any participant admin can create, alter, or remove CSV census rows, which can corrupt verification data relied on by authorization workflows.

Patches

See https://github.com/decidim/decidim/pull/16674 and https://github.com/decidim/decidim/pull/16703

Workarounds

Disable Organization Census verification method

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.

Description

Scanned identity-document images provided by participants and shown in the verification admin workflow are exposed through signed /rails/active_storage/disk/ URLs that can be fetched without any authenticated session.

Anyone who obtains one of those URLs can retrieve the document until the signature expires.

Technical description

This issue comes from the verification admin UI exposing scanned documents through reusable Active Storage disk links. Verification-document images are rendered with variant_url(...), which produces signed /rails/active_storage/disk/... links instead of routing the file through an authorization-checking controller. Because Decidim configures Active Storage service URLs to remain valid for seven days, the URL itself becomes the credential for that period.

The affected files are verification_attachment blobs on Decidim::Authorization, and the admin review pages embed those signed URLs directly into the HTML for pending and confirmation views.

Reproduction steps:

1. Create a fresh verification document as a normal user. 1.1. Open http://localhost:3001/users/sign_in. 1.2. Open http://localhost:3001/id_documents/authorizations/new. 1.3. Submit an id_documents verification request with an image attachment.

2. Open the admin review page that renders the attachment. 2.1. Sign out. 2.2. Sign back in as admin@example.org. 2.3. Try http://localhost:3001/admin/id_documents.

3. Harvest the signed Active Storage URL. 3.1. Open DevTools Network before loading the review page. 3.2. Reload the page. 3.3. Copy one request URL matching http://localhost:3001/rails/active_storage/disk/<SIGNED_TOKEN>/<FILENAME>.

4. Replay the file URL without any Decidim session. 4.1. Open a private window or a second browser where you are not signed in to Decidim. 4.2. Paste the exact copied /rails/active_storage/disk/... URL. 4.3. Confirm the verification image still loads.

Impact

• This only applies to Organizations using the "Identity documents" verification
• Any party that obtains one of these URLs can download the underlying scanned identity document for the lifetime of the signed link without needing to authenticate as the reviewing admin.
• In the reproduced case, that replay window was about seven days, which is long enough for routine leakage channels such as copied links, screenshots, logs, browser history, and support workflows to become realistic exfiltration paths.
• This raises the risk of leakage through browser history, screenshots, copy-paste, support tickets, logs, analytics tooling, malicious browser extensions, or any other channel that captures full URLs.
• Because the affected files are identity-verification documents, the exposed data can include highly sensitive personal information.

Patches

See https://github.com/decidim/decidim/pull/16680

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.

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.

Description

A participant manager can access and modify the CSV census record admin forms.

Technical description

The CSV census admin record-management surface under /admin/csv_census/census_logs does not enforce admin-only authorization before rendering or mutating Decidim::Verifications::CsvDatum.

A participant manager (which can only manage participants) can therefore open the admin forms, create or update census rows, and delete rows directly.

Reproduction steps:

1. Sign in a participant admin and open http://localhost:3000/admin/csv_census/census_logs/new_record in the browser. Confirm the create form loads even though the session is not a full admin.

Note that normal participant accounts were not able to access the CSV census records which is good.

Impact

Any participant admin can create, alter, or remove CSV census rows, which can corrupt verification data relied on by authorization workflows.

Patches

See https://github.com/decidim/decidim/pull/16674 and https://github.com/decidim/decidim/pull/16703

Workarounds

Disable Organization Census verification method

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.

Description

Scanned identity-document images provided by participants and shown in the verification admin workflow are exposed through signed /rails/active_storage/disk/ URLs that can be fetched without any authenticated session.

Anyone who obtains one of those URLs can retrieve the document until the signature expires.

Technical description

This issue comes from the verification admin UI exposing scanned documents through reusable Active Storage disk links. Verification-document images are rendered with variant_url(...), which produces signed /rails/active_storage/disk/... links instead of routing the file through an authorization-checking controller. Because Decidim configures Active Storage service URLs to remain valid for seven days, the URL itself becomes the credential for that period.

The affected files are verification_attachment blobs on Decidim::Authorization, and the admin review pages embed those signed URLs directly into the HTML for pending and confirmation views.

Reproduction steps:

1. Create a fresh verification document as a normal user. 1.1. Open http://localhost:3001/users/sign_in. 1.2. Open http://localhost:3001/id_documents/authorizations/new. 1.3. Submit an id_documents verification request with an image attachment.

2. Open the admin review page that renders the attachment. 2.1. Sign out. 2.2. Sign back in as admin@example.org. 2.3. Try http://localhost:3001/admin/id_documents.

3. Harvest the signed Active Storage URL. 3.1. Open DevTools Network before loading the review page. 3.2. Reload the page. 3.3. Copy one request URL matching http://localhost:3001/rails/active_storage/disk/<SIGNED_TOKEN>/<FILENAME>.

4. Replay the file URL without any Decidim session. 4.1. Open a private window or a second browser where you are not signed in to Decidim. 4.2. Paste the exact copied /rails/active_storage/disk/... URL. 4.3. Confirm the verification image still loads.

Impact

• This only applies to Organizations using the "Identity documents" verification
• Any party that obtains one of these URLs can download the underlying scanned identity document for the lifetime of the signed link without needing to authenticate as the reviewing admin.
• In the reproduced case, that replay window was about seven days, which is long enough for routine leakage channels such as copied links, screenshots, logs, browser history, and support workflows to become realistic exfiltration paths.
• This raises the risk of leakage through browser history, screenshots, copy-paste, support tickets, logs, analytics tooling, malicious browser extensions, or any other channel that captures full URLs.
• Because the affected files are identity-verification documents, the exposed data can include highly sensitive personal information.

Patches

See https://github.com/decidim/decidim/pull/16680

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.

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.

Description

A participant manager can access and modify the CSV census record admin forms.

Technical description

The CSV census admin record-management surface under /admin/csv_census/census_logs does not enforce admin-only authorization before rendering or mutating Decidim::Verifications::CsvDatum.

A participant manager (which can only manage participants) can therefore open the admin forms, create or update census rows, and delete rows directly.

Reproduction steps:

1. Sign in a participant admin and open http://localhost:3000/admin/csv_census/census_logs/new_record in the browser. Confirm the create form loads even though the session is not a full admin.

Note that normal participant accounts were not able to access the CSV census records which is good.

Impact

Any participant admin can create, alter, or remove CSV census rows, which can corrupt verification data relied on by authorization workflows.

Patches

See https://github.com/decidim/decidim/pull/16674 and https://github.com/decidim/decidim/pull/16703

Workarounds

Disable Organization Census verification method

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.

Description

Scanned identity-document images provided by participants and shown in the verification admin workflow are exposed through signed /rails/active_storage/disk/ URLs that can be fetched without any authenticated session.

Anyone who obtains one of those URLs can retrieve the document until the signature expires.

Technical description

This issue comes from the verification admin UI exposing scanned documents through reusable Active Storage disk links. Verification-document images are rendered with variant_url(...), which produces signed /rails/active_storage/disk/... links instead of routing the file through an authorization-checking controller. Because Decidim configures Active Storage service URLs to remain valid for seven days, the URL itself becomes the credential for that period.

The affected files are verification_attachment blobs on Decidim::Authorization, and the admin review pages embed those signed URLs directly into the HTML for pending and confirmation views.

Reproduction steps:

1. Create a fresh verification document as a normal user. 1.1. Open http://localhost:3001/users/sign_in. 1.2. Open http://localhost:3001/id_documents/authorizations/new. 1.3. Submit an id_documents verification request with an image attachment.

2. Open the admin review page that renders the attachment. 2.1. Sign out. 2.2. Sign back in as admin@example.org. 2.3. Try http://localhost:3001/admin/id_documents.

3. Harvest the signed Active Storage URL. 3.1. Open DevTools Network before loading the review page. 3.2. Reload the page. 3.3. Copy one request URL matching http://localhost:3001/rails/active_storage/disk/<SIGNED_TOKEN>/<FILENAME>.

4. Replay the file URL without any Decidim session. 4.1. Open a private window or a second browser where you are not signed in to Decidim. 4.2. Paste the exact copied /rails/active_storage/disk/... URL. 4.3. Confirm the verification image still loads.

Impact

• This only applies to Organizations using the "Identity documents" verification
• Any party that obtains one of these URLs can download the underlying scanned identity document for the lifetime of the signed link without needing to authenticate as the reviewing admin.
• In the reproduced case, that replay window was about seven days, which is long enough for routine leakage channels such as copied links, screenshots, logs, browser history, and support workflows to become realistic exfiltration paths.
• This raises the risk of leakage through browser history, screenshots, copy-paste, support tickets, logs, analytics tooling, malicious browser extensions, or any other channel that captures full URLs.
• Because the affected files are identity-verification documents, the exposed data can include highly sensitive personal information.

Patches

See https://github.com/decidim/decidim/pull/16680

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.

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.

Description

A participant manager can access and modify the CSV census record admin forms.

Technical description

The CSV census admin record-management surface under /admin/csv_census/census_logs does not enforce admin-only authorization before rendering or mutating Decidim::Verifications::CsvDatum.

A participant manager (which can only manage participants) can therefore open the admin forms, create or update census rows, and delete rows directly.

Reproduction steps:

1. Sign in a participant admin and open http://localhost:3000/admin/csv_census/census_logs/new_record in the browser. Confirm the create form loads even though the session is not a full admin.

Note that normal participant accounts were not able to access the CSV census records which is good.

Impact

Any participant admin can create, alter, or remove CSV census rows, which can corrupt verification data relied on by authorization workflows.

Patches

See https://github.com/decidim/decidim/pull/16674 and https://github.com/decidim/decidim/pull/16703

Workarounds

Disable Organization Census verification method

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.

Description

Scanned identity-document images provided by participants and shown in the verification admin workflow are exposed through signed /rails/active_storage/disk/ URLs that can be fetched without any authenticated session.

Anyone who obtains one of those URLs can retrieve the document until the signature expires.

Technical description

This issue comes from the verification admin UI exposing scanned documents through reusable Active Storage disk links. Verification-document images are rendered with variant_url(...), which produces signed /rails/active_storage/disk/... links instead of routing the file through an authorization-checking controller. Because Decidim configures Active Storage service URLs to remain valid for seven days, the URL itself becomes the credential for that period.

The affected files are verification_attachment blobs on Decidim::Authorization, and the admin review pages embed those signed URLs directly into the HTML for pending and confirmation views.

Reproduction steps:

1. Create a fresh verification document as a normal user. 1.1. Open http://localhost:3001/users/sign_in. 1.2. Open http://localhost:3001/id_documents/authorizations/new. 1.3. Submit an id_documents verification request with an image attachment.

2. Open the admin review page that renders the attachment. 2.1. Sign out. 2.2. Sign back in as admin@example.org. 2.3. Try http://localhost:3001/admin/id_documents.

3. Harvest the signed Active Storage URL. 3.1. Open DevTools Network before loading the review page. 3.2. Reload the page. 3.3. Copy one request URL matching http://localhost:3001/rails/active_storage/disk/<SIGNED_TOKEN>/<FILENAME>.

4. Replay the file URL without any Decidim session. 4.1. Open a private window or a second browser where you are not signed in to Decidim. 4.2. Paste the exact copied /rails/active_storage/disk/... URL. 4.3. Confirm the verification image still loads.

Impact

• This only applies to Organizations using the "Identity documents" verification
• Any party that obtains one of these URLs can download the underlying scanned identity document for the lifetime of the signed link without needing to authenticate as the reviewing admin.
• In the reproduced case, that replay window was about seven days, which is long enough for routine leakage channels such as copied links, screenshots, logs, browser history, and support workflows to become realistic exfiltration paths.
• This raises the risk of leakage through browser history, screenshots, copy-paste, support tickets, logs, analytics tooling, malicious browser extensions, or any other channel that captures full URLs.
• Because the affected files are identity-verification documents, the exposed data can include highly sensitive personal information.

Patches

See https://github.com/decidim/decidim/pull/16680

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.

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.

Description

A participant manager can access and modify the CSV census record admin forms.

Technical description

The CSV census admin record-management surface under /admin/csv_census/census_logs does not enforce admin-only authorization before rendering or mutating Decidim::Verifications::CsvDatum.

A participant manager (which can only manage participants) can therefore open the admin forms, create or update census rows, and delete rows directly.

Reproduction steps:

1. Sign in a participant admin and open http://localhost:3000/admin/csv_census/census_logs/new_record in the browser. Confirm the create form loads even though the session is not a full admin.

Note that normal participant accounts were not able to access the CSV census records which is good.

Impact

Any participant admin can create, alter, or remove CSV census rows, which can corrupt verification data relied on by authorization workflows.

Patches

See https://github.com/decidim/decidim/pull/16674 and https://github.com/decidim/decidim/pull/16703

Workarounds

Disable Organization Census verification method

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.

Description

Scanned identity-document images provided by participants and shown in the verification admin workflow are exposed through signed /rails/active_storage/disk/ URLs that can be fetched without any authenticated session.

Anyone who obtains one of those URLs can retrieve the document until the signature expires.

Technical description

This issue comes from the verification admin UI exposing scanned documents through reusable Active Storage disk links. Verification-document images are rendered with variant_url(...), which produces signed /rails/active_storage/disk/... links instead of routing the file through an authorization-checking controller. Because Decidim configures Active Storage service URLs to remain valid for seven days, the URL itself becomes the credential for that period.

The affected files are verification_attachment blobs on Decidim::Authorization, and the admin review pages embed those signed URLs directly into the HTML for pending and confirmation views.

Reproduction steps:

1. Create a fresh verification document as a normal user. 1.1. Open http://localhost:3001/users/sign_in. 1.2. Open http://localhost:3001/id_documents/authorizations/new. 1.3. Submit an id_documents verification request with an image attachment.

2. Open the admin review page that renders the attachment. 2.1. Sign out. 2.2. Sign back in as admin@example.org. 2.3. Try http://localhost:3001/admin/id_documents.

3. Harvest the signed Active Storage URL. 3.1. Open DevTools Network before loading the review page. 3.2. Reload the page. 3.3. Copy one request URL matching http://localhost:3001/rails/active_storage/disk/<SIGNED_TOKEN>/<FILENAME>.

4. Replay the file URL without any Decidim session. 4.1. Open a private window or a second browser where you are not signed in to Decidim. 4.2. Paste the exact copied /rails/active_storage/disk/... URL. 4.3. Confirm the verification image still loads.

Impact

• This only applies to Organizations using the "Identity documents" verification
• Any party that obtains one of these URLs can download the underlying scanned identity document for the lifetime of the signed link without needing to authenticate as the reviewing admin.
• In the reproduced case, that replay window was about seven days, which is long enough for routine leakage channels such as copied links, screenshots, logs, browser history, and support workflows to become realistic exfiltration paths.
• This raises the risk of leakage through browser history, screenshots, copy-paste, support tickets, logs, analytics tooling, malicious browser extensions, or any other channel that captures full URLs.
• Because the affected files are identity-verification documents, the exposed data can include highly sensitive personal information.

Patches

See https://github.com/decidim/decidim/pull/16680

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.

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.

Description

A participant manager can access and modify the CSV census record admin forms.

Technical description

The CSV census admin record-management surface under /admin/csv_census/census_logs does not enforce admin-only authorization before rendering or mutating Decidim::Verifications::CsvDatum.

A participant manager (which can only manage participants) can therefore open the admin forms, create or update census rows, and delete rows directly.

Reproduction steps:

1. Sign in a participant admin and open http://localhost:3000/admin/csv_census/census_logs/new_record in the browser. Confirm the create form loads even though the session is not a full admin.

Note that normal participant accounts were not able to access the CSV census records which is good.

Impact

Any participant admin can create, alter, or remove CSV census rows, which can corrupt verification data relied on by authorization workflows.

Patches

See https://github.com/decidim/decidim/pull/16674 and https://github.com/decidim/decidim/pull/16703

Workarounds

Disable Organization Census verification method

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.

Description

Scanned identity-document images provided by participants and shown in the verification admin workflow are exposed through signed /rails/active_storage/disk/ URLs that can be fetched without any authenticated session.

Anyone who obtains one of those URLs can retrieve the document until the signature expires.

Technical description

This issue comes from the verification admin UI exposing scanned documents through reusable Active Storage disk links. Verification-document images are rendered with variant_url(...), which produces signed /rails/active_storage/disk/... links instead of routing the file through an authorization-checking controller. Because Decidim configures Active Storage service URLs to remain valid for seven days, the URL itself becomes the credential for that period.

The affected files are verification_attachment blobs on Decidim::Authorization, and the admin review pages embed those signed URLs directly into the HTML for pending and confirmation views.

Reproduction steps:

1. Create a fresh verification document as a normal user. 1.1. Open http://localhost:3001/users/sign_in. 1.2. Open http://localhost:3001/id_documents/authorizations/new. 1.3. Submit an id_documents verification request with an image attachment.

2. Open the admin review page that renders the attachment. 2.1. Sign out. 2.2. Sign back in as admin@example.org. 2.3. Try http://localhost:3001/admin/id_documents.

3. Harvest the signed Active Storage URL. 3.1. Open DevTools Network before loading the review page. 3.2. Reload the page. 3.3. Copy one request URL matching http://localhost:3001/rails/active_storage/disk/<SIGNED_TOKEN>/<FILENAME>.

4. Replay the file URL without any Decidim session. 4.1. Open a private window or a second browser where you are not signed in to Decidim. 4.2. Paste the exact copied /rails/active_storage/disk/... URL. 4.3. Confirm the verification image still loads.

Impact

• This only applies to Organizations using the "Identity documents" verification
• Any party that obtains one of these URLs can download the underlying scanned identity document for the lifetime of the signed link without needing to authenticate as the reviewing admin.
• In the reproduced case, that replay window was about seven days, which is long enough for routine leakage channels such as copied links, screenshots, logs, browser history, and support workflows to become realistic exfiltration paths.
• This raises the risk of leakage through browser history, screenshots, copy-paste, support tickets, logs, analytics tooling, malicious browser extensions, or any other channel that captures full URLs.
• Because the affected files are identity-verification documents, the exposed data can include highly sensitive personal information.

Patches

See https://github.com/decidim/decidim/pull/16680

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.

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.

Description

A participant manager can access and modify the CSV census record admin forms.

Technical description

The CSV census admin record-management surface under /admin/csv_census/census_logs does not enforce admin-only authorization before rendering or mutating Decidim::Verifications::CsvDatum.

A participant manager (which can only manage participants) can therefore open the admin forms, create or update census rows, and delete rows directly.

Reproduction steps:

1. Sign in a participant admin and open http://localhost:3000/admin/csv_census/census_logs/new_record in the browser. Confirm the create form loads even though the session is not a full admin.

Note that normal participant accounts were not able to access the CSV census records which is good.

Impact

Any participant admin can create, alter, or remove CSV census rows, which can corrupt verification data relied on by authorization workflows.

Patches

See https://github.com/decidim/decidim/pull/16674 and https://github.com/decidim/decidim/pull/16703

Workarounds

Disable Organization Census verification method

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.

Description

Scanned identity-document images provided by participants and shown in the verification admin workflow are exposed through signed /rails/active_storage/disk/ URLs that can be fetched without any authenticated session.

Anyone who obtains one of those URLs can retrieve the document until the signature expires.

Technical description

This issue comes from the verification admin UI exposing scanned documents through reusable Active Storage disk links. Verification-document images are rendered with variant_url(...), which produces signed /rails/active_storage/disk/... links instead of routing the file through an authorization-checking controller. Because Decidim configures Active Storage service URLs to remain valid for seven days, the URL itself becomes the credential for that period.

The affected files are verification_attachment blobs on Decidim::Authorization, and the admin review pages embed those signed URLs directly into the HTML for pending and confirmation views.

Reproduction steps:

1. Create a fresh verification document as a normal user. 1.1. Open http://localhost:3001/users/sign_in. 1.2. Open http://localhost:3001/id_documents/authorizations/new. 1.3. Submit an id_documents verification request with an image attachment.

2. Open the admin review page that renders the attachment. 2.1. Sign out. 2.2. Sign back in as admin@example.org. 2.3. Try http://localhost:3001/admin/id_documents.

3. Harvest the signed Active Storage URL. 3.1. Open DevTools Network before loading the review page. 3.2. Reload the page. 3.3. Copy one request URL matching http://localhost:3001/rails/active_storage/disk/<SIGNED_TOKEN>/<FILENAME>.

4. Replay the file URL without any Decidim session. 4.1. Open a private window or a second browser where you are not signed in to Decidim. 4.2. Paste the exact copied /rails/active_storage/disk/... URL. 4.3. Confirm the verification image still loads.

Impact

• This only applies to Organizations using the "Identity documents" verification
• Any party that obtains one of these URLs can download the underlying scanned identity document for the lifetime of the signed link without needing to authenticate as the reviewing admin.
• In the reproduced case, that replay window was about seven days, which is long enough for routine leakage channels such as copied links, screenshots, logs, browser history, and support workflows to become realistic exfiltration paths.
• This raises the risk of leakage through browser history, screenshots, copy-paste, support tickets, logs, analytics tooling, malicious browser extensions, or any other channel that captures full URLs.
• Because the affected files are identity-verification documents, the exposed data can include highly sensitive personal information.

Patches

See https://github.com/decidim/decidim/pull/16680

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.

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.

Description

A participant manager can access and modify the CSV census record admin forms.

Technical description

The CSV census admin record-management surface under /admin/csv_census/census_logs does not enforce admin-only authorization before rendering or mutating Decidim::Verifications::CsvDatum.

A participant manager (which can only manage participants) can therefore open the admin forms, create or update census rows, and delete rows directly.

Reproduction steps:

1. Sign in a participant admin and open http://localhost:3000/admin/csv_census/census_logs/new_record in the browser. Confirm the create form loads even though the session is not a full admin.

Note that normal participant accounts were not able to access the CSV census records which is good.

Impact

Any participant admin can create, alter, or remove CSV census rows, which can corrupt verification data relied on by authorization workflows.

Patches

See https://github.com/decidim/decidim/pull/16674 and https://github.com/decidim/decidim/pull/16703

Workarounds

Disable Organization Census verification method

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.

Description

Scanned identity-document images provided by participants and shown in the verification admin workflow are exposed through signed /rails/active_storage/disk/ URLs that can be fetched without any authenticated session.

Anyone who obtains one of those URLs can retrieve the document until the signature expires.

Technical description

This issue comes from the verification admin UI exposing scanned documents through reusable Active Storage disk links. Verification-document images are rendered with variant_url(...), which produces signed /rails/active_storage/disk/... links instead of routing the file through an authorization-checking controller. Because Decidim configures Active Storage service URLs to remain valid for seven days, the URL itself becomes the credential for that period.

The affected files are verification_attachment blobs on Decidim::Authorization, and the admin review pages embed those signed URLs directly into the HTML for pending and confirmation views.

Reproduction steps:

1. Create a fresh verification document as a normal user. 1.1. Open http://localhost:3001/users/sign_in. 1.2. Open http://localhost:3001/id_documents/authorizations/new. 1.3. Submit an id_documents verification request with an image attachment.

2. Open the admin review page that renders the attachment. 2.1. Sign out. 2.2. Sign back in as admin@example.org. 2.3. Try http://localhost:3001/admin/id_documents.

3. Harvest the signed Active Storage URL. 3.1. Open DevTools Network before loading the review page. 3.2. Reload the page. 3.3. Copy one request URL matching http://localhost:3001/rails/active_storage/disk/<SIGNED_TOKEN>/<FILENAME>.

4. Replay the file URL without any Decidim session. 4.1. Open a private window or a second browser where you are not signed in to Decidim. 4.2. Paste the exact copied /rails/active_storage/disk/... URL. 4.3. Confirm the verification image still loads.

Impact

• This only applies to Organizations using the "Identity documents" verification
• Any party that obtains one of these URLs can download the underlying scanned identity document for the lifetime of the signed link without needing to authenticate as the reviewing admin.
• In the reproduced case, that replay window was about seven days, which is long enough for routine leakage channels such as copied links, screenshots, logs, browser history, and support workflows to become realistic exfiltration paths.
• This raises the risk of leakage through browser history, screenshots, copy-paste, support tickets, logs, analytics tooling, malicious browser extensions, or any other channel that captures full URLs.
• Because the affected files are identity-verification documents, the exposed data can include highly sensitive personal information.

Patches

See https://github.com/decidim/decidim/pull/16680

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.

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.

Description

A participant manager can access and modify the CSV census record admin forms.

Technical description

The CSV census admin record-management surface under /admin/csv_census/census_logs does not enforce admin-only authorization before rendering or mutating Decidim::Verifications::CsvDatum.

A participant manager (which can only manage participants) can therefore open the admin forms, create or update census rows, and delete rows directly.

Reproduction steps:

1. Sign in a participant admin and open http://localhost:3000/admin/csv_census/census_logs/new_record in the browser. Confirm the create form loads even though the session is not a full admin.

Note that normal participant accounts were not able to access the CSV census records which is good.

Impact

Any participant admin can create, alter, or remove CSV census rows, which can corrupt verification data relied on by authorization workflows.

Patches

See https://github.com/decidim/decidim/pull/16674 and https://github.com/decidim/decidim/pull/16703

Workarounds

Disable Organization Census verification method

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.

Description

Scanned identity-document images provided by participants and shown in the verification admin workflow are exposed through signed /rails/active_storage/disk/ URLs that can be fetched without any authenticated session.

Anyone who obtains one of those URLs can retrieve the document until the signature expires.

Technical description

This issue comes from the verification admin UI exposing scanned documents through reusable Active Storage disk links. Verification-document images are rendered with variant_url(...), which produces signed /rails/active_storage/disk/... links instead of routing the file through an authorization-checking controller. Because Decidim configures Active Storage service URLs to remain valid for seven days, the URL itself becomes the credential for that period.

The affected files are verification_attachment blobs on Decidim::Authorization, and the admin review pages embed those signed URLs directly into the HTML for pending and confirmation views.

Reproduction steps:

1. Create a fresh verification document as a normal user. 1.1. Open http://localhost:3001/users/sign_in. 1.2. Open http://localhost:3001/id_documents/authorizations/new. 1.3. Submit an id_documents verification request with an image attachment.

2. Open the admin review page that renders the attachment. 2.1. Sign out. 2.2. Sign back in as admin@example.org. 2.3. Try http://localhost:3001/admin/id_documents.

3. Harvest the signed Active Storage URL. 3.1. Open DevTools Network before loading the review page. 3.2. Reload the page. 3.3. Copy one request URL matching http://localhost:3001/rails/active_storage/disk/<SIGNED_TOKEN>/<FILENAME>.

4. Replay the file URL without any Decidim session. 4.1. Open a private window or a second browser where you are not signed in to Decidim. 4.2. Paste the exact copied /rails/active_storage/disk/... URL. 4.3. Confirm the verification image still loads.

Impact

• This only applies to Organizations using the "Identity documents" verification
• Any party that obtains one of these URLs can download the underlying scanned identity document for the lifetime of the signed link without needing to authenticate as the reviewing admin.
• In the reproduced case, that replay window was about seven days, which is long enough for routine leakage channels such as copied links, screenshots, logs, browser history, and support workflows to become realistic exfiltration paths.
• This raises the risk of leakage through browser history, screenshots, copy-paste, support tickets, logs, analytics tooling, malicious browser extensions, or any other channel that captures full URLs.
• Because the affected files are identity-verification documents, the exposed data can include highly sensitive personal information.

Patches

See https://github.com/decidim/decidim/pull/16680

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.

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.

Description

A participant manager can access and modify the CSV census record admin forms.

Technical description

The CSV census admin record-management surface under /admin/csv_census/census_logs does not enforce admin-only authorization before rendering or mutating Decidim::Verifications::CsvDatum.

A participant manager (which can only manage participants) can therefore open the admin forms, create or update census rows, and delete rows directly.

Reproduction steps:

1. Sign in a participant admin and open http://localhost:3000/admin/csv_census/census_logs/new_record in the browser. Confirm the create form loads even though the session is not a full admin.

Note that normal participant accounts were not able to access the CSV census records which is good.

Impact

Any participant admin can create, alter, or remove CSV census rows, which can corrupt verification data relied on by authorization workflows.

Patches

See https://github.com/decidim/decidim/pull/16674 and https://github.com/decidim/decidim/pull/16703

Workarounds

Disable Organization Census verification method

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.

Description

Scanned identity-document images provided by participants and shown in the verification admin workflow are exposed through signed /rails/active_storage/disk/ URLs that can be fetched without any authenticated session.

Anyone who obtains one of those URLs can retrieve the document until the signature expires.

Technical description

This issue comes from the verification admin UI exposing scanned documents through reusable Active Storage disk links. Verification-document images are rendered with variant_url(...), which produces signed /rails/active_storage/disk/... links instead of routing the file through an authorization-checking controller. Because Decidim configures Active Storage service URLs to remain valid for seven days, the URL itself becomes the credential for that period.

The affected files are verification_attachment blobs on Decidim::Authorization, and the admin review pages embed those signed URLs directly into the HTML for pending and confirmation views.

Reproduction steps:

1. Create a fresh verification document as a normal user. 1.1. Open http://localhost:3001/users/sign_in. 1.2. Open http://localhost:3001/id_documents/authorizations/new. 1.3. Submit an id_documents verification request with an image attachment.

2. Open the admin review page that renders the attachment. 2.1. Sign out. 2.2. Sign back in as admin@example.org. 2.3. Try http://localhost:3001/admin/id_documents.

3. Harvest the signed Active Storage URL. 3.1. Open DevTools Network before loading the review page. 3.2. Reload the page. 3.3. Copy one request URL matching http://localhost:3001/rails/active_storage/disk/<SIGNED_TOKEN>/<FILENAME>.

4. Replay the file URL without any Decidim session. 4.1. Open a private window or a second browser where you are not signed in to Decidim. 4.2. Paste the exact copied /rails/active_storage/disk/... URL. 4.3. Confirm the verification image still loads.

Impact

• This only applies to Organizations using the "Identity documents" verification
• Any party that obtains one of these URLs can download the underlying scanned identity document for the lifetime of the signed link without needing to authenticate as the reviewing admin.
• In the reproduced case, that replay window was about seven days, which is long enough for routine leakage channels such as copied links, screenshots, logs, browser history, and support workflows to become realistic exfiltration paths.
• This raises the risk of leakage through browser history, screenshots, copy-paste, support tickets, logs, analytics tooling, malicious browser extensions, or any other channel that captures full URLs.
• Because the affected files are identity-verification documents, the exposed data can include highly sensitive personal information.

Patches

See https://github.com/decidim/decidim/pull/16680

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.

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.