decidim-core

Description

The push-subscription endpoint stores an attacker-controlled delivery URL, and the notification send path becomes an outbound-request sink when VAPID delivery is enabled. The practical result is an authenticated, stored, mostly blind SSRF primitive to arbitrary HTTPS endpoints reachable from the app server.

Technical description

When VAPID delivery is enabled, the notification subscription flow stores the client-supplied push endpoint without checking that it belongs to an approved push service. The send path later passes that stored URL to WebPush.payload_send, turning the subscription into an attacker-controlled outbound request destination. This is the source-to-sink chain:

1. Source: attacker-controlled subscription.endpoint in the JSON body posted to POST /notifications_subscriptions.
2. Persistence: params[:endpoint] is stored under user.notification_settings["subscriptions"].
3. Retrieval: user.notifications_subscriptions.values returns that stored endpoint later.
4. Sink: build_payload sets endpoint: subscription["endpoint"].
5. Outbound request: WebPush.payload_send(**payload) uses the attacker-supplied endpoint as the destination.

One spec asserts that the endpoint is persisted exactly as supplied:

# decidim-core/spec/services/decidim/notifications_subscriptions_persistor_spec.rb
expect(user.notifications_subscriptions["auth_code_121"]["endpoint"]).to eq(params[:endpoint])

Another spec asserts that SendPushNotification passes the stored endpoint into WebPush.payload_send:

# decidim-core/spec/services/decidim/send_push_notification_spec.rb
first_notification_payload = {
  message:,
  endpoint: subscriptions["auth_key_1"]["endpoint"],
  p256dh: subscriptions["auth_key_1"]["p256dh"],
  auth: subscriptions["auth_key_1"]["auth"],
  vapid: a_hash_including(...)
}
expect(WebPush).to receive(:payload_send).with(first_notification_payload)

Impact

• In a configured deployment, an authenticated user can register an attacker-controlled or otherwise unauthorized HTTPS URL.
• The server then sends outbound POST requests there whenever a notification is pushed.
• This is a stored, mostly blind SSRF primitive: useful for outbound interaction with attacker infrastructure and, where routable, internal HTTPS services.
• Notification metadata is disclosed to the supplied endpoint through the encrypted web push request path.

Patches

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

Workarounds

Disable the push notifications feature by removing the VAPID keys in the server.

Resource

SSRF

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 privileged admin user who can edit an affected landing page can store arbitrary HTML/JavaScript in an HTML block, and the public page renders it with html_safe and no output escaping.

Technical description

This issue lets any admin who can edit an affected landing page store arbitrary HTML and JavaScript in an HTML block. The block is then rendered back through Decidim::ContentBlocks::HtmlCell#html_content without a sanitization boundary, so the script executes later in visitor's browsers.

Impact

• A user with landing-page editing rights for an affected scope can persist JavaScript that executes in visitor's browsers on that page.
• Because exploitation already requires privileged administrative access, the practical risk is lower than a participant-controlled or unauthenticated stored XSS. It still creates a browser-execution primitive in a trusted admin-editable surface.

Patches

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

Workarounds

Do not give admin permissions to non-trustful users.

Reference

Stored XSS

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 normal download_your_data flow requires the requester to be logged in as the export owner, but the resulting Active Storage blob redirect URL can be replayed without authentication by anyone who obtains it.

Technical description

This private export flow turns an authenticated, user-scoped download into a reusable bearer link because the protected Decidim endpoint redirects to the underlying Active Storage blob URL. Decidim::DownloadYourDataController#download_file correctly scopes the export record to current_user, so the wrapper route itself is not directly accessible to another user. However, once the owner performs that authenticated GET request, the response redirects to a signed Active Storage URL that is no longer bound to the user session. Anyone who learns that URL can replay it and retrieve the file without being logged in as the export owner.

Because the blob redirect URL is delivered through a GET request and appears in the redirect chain, it is more likely to leak through browser history, logs, proxy tooling, screenshots, copied links, support transcripts, or other client-side handling of URLs.

Reproduction steps:

Step 1. Generate or locate a completed export in the Web UI.

1. Sign in as user@example.org at http://localhost:3001/users/sign_in.
2. Open http://localhost:3001/download_your_data.
3. Request a new export from the page and wait until the export becomes downloadable.
4. Open the completed export entry from the list and copy its wrapper URL, for example http://localhost:3001/download_your_data/download?uuid=07286e61-932d-46d4-bd74-bcd1340c503f .

Step 2. Download through the authenticated wrapper route.

1. While still signed in as user@example.org, open the wrapper URL in the browser.
2. Confirm that this Decidim route requires the owner session and is not directly usable when logged out or when logged in as another user.

Step 3. Capture the final bearer URL in the redirect chain.

1. In DevTools Network or Burp, inspect the redirect sequence for the wrapper request.
2. Copy the Active Storage redirect URL, typically matching http://localhost:3001/rails/active_storage/blobs/redirect/<SIGNED_ID>/<FILENAME>.
3. Note that the Active Storage redirect URL is no longer protected by the Decidim ownership check.

Step 4. Replay the final file URL without authentication.

1. Open a private window or separate browser with no Decidim session.
2. Paste the copied http://localhost:3001/rails/active_storage/blobs/redirect/<SIGNED_ID>/<FILENAME> URL.
3. Confirm the export file still downloads even though you are not logged in as the export owner.

Impact

Personal data exports can be retrieved through leakage channels such as browser history, logs, referrers, screenshots, copied links, support transcripts, intercepted email content, or other client-side disclosure of the GET URL.

Patches

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

Workarounds

Disable Private Downloads URLs

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 push-subscription endpoint stores an attacker-controlled delivery URL, and the notification send path becomes an outbound-request sink when VAPID delivery is enabled. The practical result is an authenticated, stored, mostly blind SSRF primitive to arbitrary HTTPS endpoints reachable from the app server.

Technical description

When VAPID delivery is enabled, the notification subscription flow stores the client-supplied push endpoint without checking that it belongs to an approved push service. The send path later passes that stored URL to WebPush.payload_send, turning the subscription into an attacker-controlled outbound request destination. This is the source-to-sink chain:

1. Source: attacker-controlled subscription.endpoint in the JSON body posted to POST /notifications_subscriptions.
2. Persistence: params[:endpoint] is stored under user.notification_settings["subscriptions"].
3. Retrieval: user.notifications_subscriptions.values returns that stored endpoint later.
4. Sink: build_payload sets endpoint: subscription["endpoint"].
5. Outbound request: WebPush.payload_send(**payload) uses the attacker-supplied endpoint as the destination.

One spec asserts that the endpoint is persisted exactly as supplied:

# decidim-core/spec/services/decidim/notifications_subscriptions_persistor_spec.rb
expect(user.notifications_subscriptions["auth_code_121"]["endpoint"]).to eq(params[:endpoint])

Another spec asserts that SendPushNotification passes the stored endpoint into WebPush.payload_send:

# decidim-core/spec/services/decidim/send_push_notification_spec.rb
first_notification_payload = {
  message:,
  endpoint: subscriptions["auth_key_1"]["endpoint"],
  p256dh: subscriptions["auth_key_1"]["p256dh"],
  auth: subscriptions["auth_key_1"]["auth"],
  vapid: a_hash_including(...)
}
expect(WebPush).to receive(:payload_send).with(first_notification_payload)

Impact

• In a configured deployment, an authenticated user can register an attacker-controlled or otherwise unauthorized HTTPS URL.
• The server then sends outbound POST requests there whenever a notification is pushed.
• This is a stored, mostly blind SSRF primitive: useful for outbound interaction with attacker infrastructure and, where routable, internal HTTPS services.
• Notification metadata is disclosed to the supplied endpoint through the encrypted web push request path.

Patches

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

Workarounds

Disable the push notifications feature by removing the VAPID keys in the server.

Resource

SSRF

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 privileged admin user who can edit an affected landing page can store arbitrary HTML/JavaScript in an HTML block, and the public page renders it with html_safe and no output escaping.

Technical description

This issue lets any admin who can edit an affected landing page store arbitrary HTML and JavaScript in an HTML block. The block is then rendered back through Decidim::ContentBlocks::HtmlCell#html_content without a sanitization boundary, so the script executes later in visitor's browsers.

Impact

• A user with landing-page editing rights for an affected scope can persist JavaScript that executes in visitor's browsers on that page.
• Because exploitation already requires privileged administrative access, the practical risk is lower than a participant-controlled or unauthenticated stored XSS. It still creates a browser-execution primitive in a trusted admin-editable surface.

Patches

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

Workarounds

Do not give admin permissions to non-trustful users.

Reference

Stored XSS

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 normal download_your_data flow requires the requester to be logged in as the export owner, but the resulting Active Storage blob redirect URL can be replayed without authentication by anyone who obtains it.

Technical description

This private export flow turns an authenticated, user-scoped download into a reusable bearer link because the protected Decidim endpoint redirects to the underlying Active Storage blob URL. Decidim::DownloadYourDataController#download_file correctly scopes the export record to current_user, so the wrapper route itself is not directly accessible to another user. However, once the owner performs that authenticated GET request, the response redirects to a signed Active Storage URL that is no longer bound to the user session. Anyone who learns that URL can replay it and retrieve the file without being logged in as the export owner.

Because the blob redirect URL is delivered through a GET request and appears in the redirect chain, it is more likely to leak through browser history, logs, proxy tooling, screenshots, copied links, support transcripts, or other client-side handling of URLs.

Reproduction steps:

Step 1. Generate or locate a completed export in the Web UI.

1. Sign in as user@example.org at http://localhost:3001/users/sign_in.
2. Open http://localhost:3001/download_your_data.
3. Request a new export from the page and wait until the export becomes downloadable.
4. Open the completed export entry from the list and copy its wrapper URL, for example http://localhost:3001/download_your_data/download?uuid=07286e61-932d-46d4-bd74-bcd1340c503f .

Step 2. Download through the authenticated wrapper route.

1. While still signed in as user@example.org, open the wrapper URL in the browser.
2. Confirm that this Decidim route requires the owner session and is not directly usable when logged out or when logged in as another user.

Step 3. Capture the final bearer URL in the redirect chain.

1. In DevTools Network or Burp, inspect the redirect sequence for the wrapper request.
2. Copy the Active Storage redirect URL, typically matching http://localhost:3001/rails/active_storage/blobs/redirect/<SIGNED_ID>/<FILENAME>.
3. Note that the Active Storage redirect URL is no longer protected by the Decidim ownership check.

Step 4. Replay the final file URL without authentication.

1. Open a private window or separate browser with no Decidim session.
2. Paste the copied http://localhost:3001/rails/active_storage/blobs/redirect/<SIGNED_ID>/<FILENAME> URL.
3. Confirm the export file still downloads even though you are not logged in as the export owner.

Impact

Personal data exports can be retrieved through leakage channels such as browser history, logs, referrers, screenshots, copied links, support transcripts, intercepted email content, or other client-side disclosure of the GET URL.

Patches

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

Workarounds

Disable Private Downloads URLs

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 push-subscription endpoint stores an attacker-controlled delivery URL, and the notification send path becomes an outbound-request sink when VAPID delivery is enabled. The practical result is an authenticated, stored, mostly blind SSRF primitive to arbitrary HTTPS endpoints reachable from the app server.

Technical description

When VAPID delivery is enabled, the notification subscription flow stores the client-supplied push endpoint without checking that it belongs to an approved push service. The send path later passes that stored URL to WebPush.payload_send, turning the subscription into an attacker-controlled outbound request destination. This is the source-to-sink chain:

1. Source: attacker-controlled subscription.endpoint in the JSON body posted to POST /notifications_subscriptions.
2. Persistence: params[:endpoint] is stored under user.notification_settings["subscriptions"].
3. Retrieval: user.notifications_subscriptions.values returns that stored endpoint later.
4. Sink: build_payload sets endpoint: subscription["endpoint"].
5. Outbound request: WebPush.payload_send(**payload) uses the attacker-supplied endpoint as the destination.

One spec asserts that the endpoint is persisted exactly as supplied:

# decidim-core/spec/services/decidim/notifications_subscriptions_persistor_spec.rb
expect(user.notifications_subscriptions["auth_code_121"]["endpoint"]).to eq(params[:endpoint])

Another spec asserts that SendPushNotification passes the stored endpoint into WebPush.payload_send:

# decidim-core/spec/services/decidim/send_push_notification_spec.rb
first_notification_payload = {
  message:,
  endpoint: subscriptions["auth_key_1"]["endpoint"],
  p256dh: subscriptions["auth_key_1"]["p256dh"],
  auth: subscriptions["auth_key_1"]["auth"],
  vapid: a_hash_including(...)
}
expect(WebPush).to receive(:payload_send).with(first_notification_payload)

Impact

• In a configured deployment, an authenticated user can register an attacker-controlled or otherwise unauthorized HTTPS URL.
• The server then sends outbound POST requests there whenever a notification is pushed.
• This is a stored, mostly blind SSRF primitive: useful for outbound interaction with attacker infrastructure and, where routable, internal HTTPS services.
• Notification metadata is disclosed to the supplied endpoint through the encrypted web push request path.

Patches

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

Workarounds

Disable the push notifications feature by removing the VAPID keys in the server.

Resource

SSRF

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 privileged admin user who can edit an affected landing page can store arbitrary HTML/JavaScript in an HTML block, and the public page renders it with html_safe and no output escaping.

Technical description

This issue lets any admin who can edit an affected landing page store arbitrary HTML and JavaScript in an HTML block. The block is then rendered back through Decidim::ContentBlocks::HtmlCell#html_content without a sanitization boundary, so the script executes later in visitor's browsers.

Impact

• A user with landing-page editing rights for an affected scope can persist JavaScript that executes in visitor's browsers on that page.
• Because exploitation already requires privileged administrative access, the practical risk is lower than a participant-controlled or unauthenticated stored XSS. It still creates a browser-execution primitive in a trusted admin-editable surface.

Patches

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

Workarounds

Do not give admin permissions to non-trustful users.

Reference

Stored XSS

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 normal download_your_data flow requires the requester to be logged in as the export owner, but the resulting Active Storage blob redirect URL can be replayed without authentication by anyone who obtains it.

Technical description

This private export flow turns an authenticated, user-scoped download into a reusable bearer link because the protected Decidim endpoint redirects to the underlying Active Storage blob URL. Decidim::DownloadYourDataController#download_file correctly scopes the export record to current_user, so the wrapper route itself is not directly accessible to another user. However, once the owner performs that authenticated GET request, the response redirects to a signed Active Storage URL that is no longer bound to the user session. Anyone who learns that URL can replay it and retrieve the file without being logged in as the export owner.

Because the blob redirect URL is delivered through a GET request and appears in the redirect chain, it is more likely to leak through browser history, logs, proxy tooling, screenshots, copied links, support transcripts, or other client-side handling of URLs.

Reproduction steps:

Step 1. Generate or locate a completed export in the Web UI.

1. Sign in as user@example.org at http://localhost:3001/users/sign_in.
2. Open http://localhost:3001/download_your_data.
3. Request a new export from the page and wait until the export becomes downloadable.
4. Open the completed export entry from the list and copy its wrapper URL, for example http://localhost:3001/download_your_data/download?uuid=07286e61-932d-46d4-bd74-bcd1340c503f .

Step 2. Download through the authenticated wrapper route.

1. While still signed in as user@example.org, open the wrapper URL in the browser.
2. Confirm that this Decidim route requires the owner session and is not directly usable when logged out or when logged in as another user.

Step 3. Capture the final bearer URL in the redirect chain.

1. In DevTools Network or Burp, inspect the redirect sequence for the wrapper request.
2. Copy the Active Storage redirect URL, typically matching http://localhost:3001/rails/active_storage/blobs/redirect/<SIGNED_ID>/<FILENAME>.
3. Note that the Active Storage redirect URL is no longer protected by the Decidim ownership check.

Step 4. Replay the final file URL without authentication.

1. Open a private window or separate browser with no Decidim session.
2. Paste the copied http://localhost:3001/rails/active_storage/blobs/redirect/<SIGNED_ID>/<FILENAME> URL.
3. Confirm the export file still downloads even though you are not logged in as the export owner.

Impact

Personal data exports can be retrieved through leakage channels such as browser history, logs, referrers, screenshots, copied links, support transcripts, intercepted email content, or other client-side disclosure of the GET URL.

Patches

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

Workarounds

Disable Private Downloads URLs

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 push-subscription endpoint stores an attacker-controlled delivery URL, and the notification send path becomes an outbound-request sink when VAPID delivery is enabled. The practical result is an authenticated, stored, mostly blind SSRF primitive to arbitrary HTTPS endpoints reachable from the app server.

Technical description

When VAPID delivery is enabled, the notification subscription flow stores the client-supplied push endpoint without checking that it belongs to an approved push service. The send path later passes that stored URL to WebPush.payload_send, turning the subscription into an attacker-controlled outbound request destination. This is the source-to-sink chain:

1. Source: attacker-controlled subscription.endpoint in the JSON body posted to POST /notifications_subscriptions.
2. Persistence: params[:endpoint] is stored under user.notification_settings["subscriptions"].
3. Retrieval: user.notifications_subscriptions.values returns that stored endpoint later.
4. Sink: build_payload sets endpoint: subscription["endpoint"].
5. Outbound request: WebPush.payload_send(**payload) uses the attacker-supplied endpoint as the destination.

One spec asserts that the endpoint is persisted exactly as supplied:

# decidim-core/spec/services/decidim/notifications_subscriptions_persistor_spec.rb
expect(user.notifications_subscriptions["auth_code_121"]["endpoint"]).to eq(params[:endpoint])

Another spec asserts that SendPushNotification passes the stored endpoint into WebPush.payload_send:

# decidim-core/spec/services/decidim/send_push_notification_spec.rb
first_notification_payload = {
  message:,
  endpoint: subscriptions["auth_key_1"]["endpoint"],
  p256dh: subscriptions["auth_key_1"]["p256dh"],
  auth: subscriptions["auth_key_1"]["auth"],
  vapid: a_hash_including(...)
}
expect(WebPush).to receive(:payload_send).with(first_notification_payload)

Impact

• In a configured deployment, an authenticated user can register an attacker-controlled or otherwise unauthorized HTTPS URL.
• The server then sends outbound POST requests there whenever a notification is pushed.
• This is a stored, mostly blind SSRF primitive: useful for outbound interaction with attacker infrastructure and, where routable, internal HTTPS services.
• Notification metadata is disclosed to the supplied endpoint through the encrypted web push request path.

Patches

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

Workarounds

Disable the push notifications feature by removing the VAPID keys in the server.

Resource

SSRF

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 privileged admin user who can edit an affected landing page can store arbitrary HTML/JavaScript in an HTML block, and the public page renders it with html_safe and no output escaping.

Technical description

This issue lets any admin who can edit an affected landing page store arbitrary HTML and JavaScript in an HTML block. The block is then rendered back through Decidim::ContentBlocks::HtmlCell#html_content without a sanitization boundary, so the script executes later in visitor's browsers.

Impact

• A user with landing-page editing rights for an affected scope can persist JavaScript that executes in visitor's browsers on that page.
• Because exploitation already requires privileged administrative access, the practical risk is lower than a participant-controlled or unauthenticated stored XSS. It still creates a browser-execution primitive in a trusted admin-editable surface.

Patches

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

Workarounds

Do not give admin permissions to non-trustful users.

Reference

Stored XSS

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 normal download_your_data flow requires the requester to be logged in as the export owner, but the resulting Active Storage blob redirect URL can be replayed without authentication by anyone who obtains it.

Technical description

This private export flow turns an authenticated, user-scoped download into a reusable bearer link because the protected Decidim endpoint redirects to the underlying Active Storage blob URL. Decidim::DownloadYourDataController#download_file correctly scopes the export record to current_user, so the wrapper route itself is not directly accessible to another user. However, once the owner performs that authenticated GET request, the response redirects to a signed Active Storage URL that is no longer bound to the user session. Anyone who learns that URL can replay it and retrieve the file without being logged in as the export owner.

Because the blob redirect URL is delivered through a GET request and appears in the redirect chain, it is more likely to leak through browser history, logs, proxy tooling, screenshots, copied links, support transcripts, or other client-side handling of URLs.

Reproduction steps:

Step 1. Generate or locate a completed export in the Web UI.

1. Sign in as user@example.org at http://localhost:3001/users/sign_in.
2. Open http://localhost:3001/download_your_data.
3. Request a new export from the page and wait until the export becomes downloadable.
4. Open the completed export entry from the list and copy its wrapper URL, for example http://localhost:3001/download_your_data/download?uuid=07286e61-932d-46d4-bd74-bcd1340c503f .

Step 2. Download through the authenticated wrapper route.

1. While still signed in as user@example.org, open the wrapper URL in the browser.
2. Confirm that this Decidim route requires the owner session and is not directly usable when logged out or when logged in as another user.

Step 3. Capture the final bearer URL in the redirect chain.

1. In DevTools Network or Burp, inspect the redirect sequence for the wrapper request.
2. Copy the Active Storage redirect URL, typically matching http://localhost:3001/rails/active_storage/blobs/redirect/<SIGNED_ID>/<FILENAME>.
3. Note that the Active Storage redirect URL is no longer protected by the Decidim ownership check.

Step 4. Replay the final file URL without authentication.

1. Open a private window or separate browser with no Decidim session.
2. Paste the copied http://localhost:3001/rails/active_storage/blobs/redirect/<SIGNED_ID>/<FILENAME> URL.
3. Confirm the export file still downloads even though you are not logged in as the export owner.

Impact

Personal data exports can be retrieved through leakage channels such as browser history, logs, referrers, screenshots, copied links, support transcripts, intercepted email content, or other client-side disclosure of the GET URL.

Patches

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

Workarounds

Disable Private Downloads URLs

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 push-subscription endpoint stores an attacker-controlled delivery URL, and the notification send path becomes an outbound-request sink when VAPID delivery is enabled. The practical result is an authenticated, stored, mostly blind SSRF primitive to arbitrary HTTPS endpoints reachable from the app server.

Technical description

When VAPID delivery is enabled, the notification subscription flow stores the client-supplied push endpoint without checking that it belongs to an approved push service. The send path later passes that stored URL to WebPush.payload_send, turning the subscription into an attacker-controlled outbound request destination. This is the source-to-sink chain:

1. Source: attacker-controlled subscription.endpoint in the JSON body posted to POST /notifications_subscriptions.
2. Persistence: params[:endpoint] is stored under user.notification_settings["subscriptions"].
3. Retrieval: user.notifications_subscriptions.values returns that stored endpoint later.
4. Sink: build_payload sets endpoint: subscription["endpoint"].
5. Outbound request: WebPush.payload_send(**payload) uses the attacker-supplied endpoint as the destination.

One spec asserts that the endpoint is persisted exactly as supplied:

# decidim-core/spec/services/decidim/notifications_subscriptions_persistor_spec.rb
expect(user.notifications_subscriptions["auth_code_121"]["endpoint"]).to eq(params[:endpoint])

Another spec asserts that SendPushNotification passes the stored endpoint into WebPush.payload_send:

# decidim-core/spec/services/decidim/send_push_notification_spec.rb
first_notification_payload = {
  message:,
  endpoint: subscriptions["auth_key_1"]["endpoint"],
  p256dh: subscriptions["auth_key_1"]["p256dh"],
  auth: subscriptions["auth_key_1"]["auth"],
  vapid: a_hash_including(...)
}
expect(WebPush).to receive(:payload_send).with(first_notification_payload)

Impact

• In a configured deployment, an authenticated user can register an attacker-controlled or otherwise unauthorized HTTPS URL.
• The server then sends outbound POST requests there whenever a notification is pushed.
• This is a stored, mostly blind SSRF primitive: useful for outbound interaction with attacker infrastructure and, where routable, internal HTTPS services.
• Notification metadata is disclosed to the supplied endpoint through the encrypted web push request path.

Patches

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

Workarounds

Disable the push notifications feature by removing the VAPID keys in the server.

Resource

SSRF

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 privileged admin user who can edit an affected landing page can store arbitrary HTML/JavaScript in an HTML block, and the public page renders it with html_safe and no output escaping.

Technical description

This issue lets any admin who can edit an affected landing page store arbitrary HTML and JavaScript in an HTML block. The block is then rendered back through Decidim::ContentBlocks::HtmlCell#html_content without a sanitization boundary, so the script executes later in visitor's browsers.

Impact

• A user with landing-page editing rights for an affected scope can persist JavaScript that executes in visitor's browsers on that page.
• Because exploitation already requires privileged administrative access, the practical risk is lower than a participant-controlled or unauthenticated stored XSS. It still creates a browser-execution primitive in a trusted admin-editable surface.

Patches

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

Workarounds

Do not give admin permissions to non-trustful users.

Reference

Stored XSS

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 normal download_your_data flow requires the requester to be logged in as the export owner, but the resulting Active Storage blob redirect URL can be replayed without authentication by anyone who obtains it.

Technical description

This private export flow turns an authenticated, user-scoped download into a reusable bearer link because the protected Decidim endpoint redirects to the underlying Active Storage blob URL. Decidim::DownloadYourDataController#download_file correctly scopes the export record to current_user, so the wrapper route itself is not directly accessible to another user. However, once the owner performs that authenticated GET request, the response redirects to a signed Active Storage URL that is no longer bound to the user session. Anyone who learns that URL can replay it and retrieve the file without being logged in as the export owner.

Because the blob redirect URL is delivered through a GET request and appears in the redirect chain, it is more likely to leak through browser history, logs, proxy tooling, screenshots, copied links, support transcripts, or other client-side handling of URLs.

Reproduction steps:

Step 1. Generate or locate a completed export in the Web UI.

1. Sign in as user@example.org at http://localhost:3001/users/sign_in.
2. Open http://localhost:3001/download_your_data.
3. Request a new export from the page and wait until the export becomes downloadable.
4. Open the completed export entry from the list and copy its wrapper URL, for example http://localhost:3001/download_your_data/download?uuid=07286e61-932d-46d4-bd74-bcd1340c503f .

Step 2. Download through the authenticated wrapper route.

1. While still signed in as user@example.org, open the wrapper URL in the browser.
2. Confirm that this Decidim route requires the owner session and is not directly usable when logged out or when logged in as another user.

Step 3. Capture the final bearer URL in the redirect chain.

1. In DevTools Network or Burp, inspect the redirect sequence for the wrapper request.
2. Copy the Active Storage redirect URL, typically matching http://localhost:3001/rails/active_storage/blobs/redirect/<SIGNED_ID>/<FILENAME>.
3. Note that the Active Storage redirect URL is no longer protected by the Decidim ownership check.

Step 4. Replay the final file URL without authentication.

1. Open a private window or separate browser with no Decidim session.
2. Paste the copied http://localhost:3001/rails/active_storage/blobs/redirect/<SIGNED_ID>/<FILENAME> URL.
3. Confirm the export file still downloads even though you are not logged in as the export owner.

Impact

Personal data exports can be retrieved through leakage channels such as browser history, logs, referrers, screenshots, copied links, support transcripts, intercepted email content, or other client-side disclosure of the GET URL.

Patches

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

Workarounds

Disable Private Downloads URLs

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 push-subscription endpoint stores an attacker-controlled delivery URL, and the notification send path becomes an outbound-request sink when VAPID delivery is enabled. The practical result is an authenticated, stored, mostly blind SSRF primitive to arbitrary HTTPS endpoints reachable from the app server.

Technical description

When VAPID delivery is enabled, the notification subscription flow stores the client-supplied push endpoint without checking that it belongs to an approved push service. The send path later passes that stored URL to WebPush.payload_send, turning the subscription into an attacker-controlled outbound request destination. This is the source-to-sink chain:

1. Source: attacker-controlled subscription.endpoint in the JSON body posted to POST /notifications_subscriptions.
2. Persistence: params[:endpoint] is stored under user.notification_settings["subscriptions"].
3. Retrieval: user.notifications_subscriptions.values returns that stored endpoint later.
4. Sink: build_payload sets endpoint: subscription["endpoint"].
5. Outbound request: WebPush.payload_send(**payload) uses the attacker-supplied endpoint as the destination.

One spec asserts that the endpoint is persisted exactly as supplied:

# decidim-core/spec/services/decidim/notifications_subscriptions_persistor_spec.rb
expect(user.notifications_subscriptions["auth_code_121"]["endpoint"]).to eq(params[:endpoint])

Another spec asserts that SendPushNotification passes the stored endpoint into WebPush.payload_send:

# decidim-core/spec/services/decidim/send_push_notification_spec.rb
first_notification_payload = {
  message:,
  endpoint: subscriptions["auth_key_1"]["endpoint"],
  p256dh: subscriptions["auth_key_1"]["p256dh"],
  auth: subscriptions["auth_key_1"]["auth"],
  vapid: a_hash_including(...)
}
expect(WebPush).to receive(:payload_send).with(first_notification_payload)

Impact

• In a configured deployment, an authenticated user can register an attacker-controlled or otherwise unauthorized HTTPS URL.
• The server then sends outbound POST requests there whenever a notification is pushed.
• This is a stored, mostly blind SSRF primitive: useful for outbound interaction with attacker infrastructure and, where routable, internal HTTPS services.
• Notification metadata is disclosed to the supplied endpoint through the encrypted web push request path.

Patches

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

Workarounds

Disable the push notifications feature by removing the VAPID keys in the server.

Resource

SSRF

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 privileged admin user who can edit an affected landing page can store arbitrary HTML/JavaScript in an HTML block, and the public page renders it with html_safe and no output escaping.

Technical description

This issue lets any admin who can edit an affected landing page store arbitrary HTML and JavaScript in an HTML block. The block is then rendered back through Decidim::ContentBlocks::HtmlCell#html_content without a sanitization boundary, so the script executes later in visitor's browsers.

Impact

• A user with landing-page editing rights for an affected scope can persist JavaScript that executes in visitor's browsers on that page.
• Because exploitation already requires privileged administrative access, the practical risk is lower than a participant-controlled or unauthenticated stored XSS. It still creates a browser-execution primitive in a trusted admin-editable surface.

Patches

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

Workarounds

Do not give admin permissions to non-trustful users.

Reference

Stored XSS

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 normal download_your_data flow requires the requester to be logged in as the export owner, but the resulting Active Storage blob redirect URL can be replayed without authentication by anyone who obtains it.

Technical description

This private export flow turns an authenticated, user-scoped download into a reusable bearer link because the protected Decidim endpoint redirects to the underlying Active Storage blob URL. Decidim::DownloadYourDataController#download_file correctly scopes the export record to current_user, so the wrapper route itself is not directly accessible to another user. However, once the owner performs that authenticated GET request, the response redirects to a signed Active Storage URL that is no longer bound to the user session. Anyone who learns that URL can replay it and retrieve the file without being logged in as the export owner.

Because the blob redirect URL is delivered through a GET request and appears in the redirect chain, it is more likely to leak through browser history, logs, proxy tooling, screenshots, copied links, support transcripts, or other client-side handling of URLs.

Reproduction steps:

Step 1. Generate or locate a completed export in the Web UI.

1. Sign in as user@example.org at http://localhost:3001/users/sign_in.
2. Open http://localhost:3001/download_your_data.
3. Request a new export from the page and wait until the export becomes downloadable.
4. Open the completed export entry from the list and copy its wrapper URL, for example http://localhost:3001/download_your_data/download?uuid=07286e61-932d-46d4-bd74-bcd1340c503f .

Step 2. Download through the authenticated wrapper route.

1. While still signed in as user@example.org, open the wrapper URL in the browser.
2. Confirm that this Decidim route requires the owner session and is not directly usable when logged out or when logged in as another user.

Step 3. Capture the final bearer URL in the redirect chain.

1. In DevTools Network or Burp, inspect the redirect sequence for the wrapper request.
2. Copy the Active Storage redirect URL, typically matching http://localhost:3001/rails/active_storage/blobs/redirect/<SIGNED_ID>/<FILENAME>.
3. Note that the Active Storage redirect URL is no longer protected by the Decidim ownership check.

Step 4. Replay the final file URL without authentication.

1. Open a private window or separate browser with no Decidim session.
2. Paste the copied http://localhost:3001/rails/active_storage/blobs/redirect/<SIGNED_ID>/<FILENAME> URL.
3. Confirm the export file still downloads even though you are not logged in as the export owner.

Impact

Personal data exports can be retrieved through leakage channels such as browser history, logs, referrers, screenshots, copied links, support transcripts, intercepted email content, or other client-side disclosure of the GET URL.

Patches

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

Workarounds

Disable Private Downloads URLs

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 push-subscription endpoint stores an attacker-controlled delivery URL, and the notification send path becomes an outbound-request sink when VAPID delivery is enabled. The practical result is an authenticated, stored, mostly blind SSRF primitive to arbitrary HTTPS endpoints reachable from the app server.

Technical description

When VAPID delivery is enabled, the notification subscription flow stores the client-supplied push endpoint without checking that it belongs to an approved push service. The send path later passes that stored URL to WebPush.payload_send, turning the subscription into an attacker-controlled outbound request destination. This is the source-to-sink chain:

1. Source: attacker-controlled subscription.endpoint in the JSON body posted to POST /notifications_subscriptions.
2. Persistence: params[:endpoint] is stored under user.notification_settings["subscriptions"].
3. Retrieval: user.notifications_subscriptions.values returns that stored endpoint later.
4. Sink: build_payload sets endpoint: subscription["endpoint"].
5. Outbound request: WebPush.payload_send(**payload) uses the attacker-supplied endpoint as the destination.

One spec asserts that the endpoint is persisted exactly as supplied:

# decidim-core/spec/services/decidim/notifications_subscriptions_persistor_spec.rb
expect(user.notifications_subscriptions["auth_code_121"]["endpoint"]).to eq(params[:endpoint])

Another spec asserts that SendPushNotification passes the stored endpoint into WebPush.payload_send:

# decidim-core/spec/services/decidim/send_push_notification_spec.rb
first_notification_payload = {
  message:,
  endpoint: subscriptions["auth_key_1"]["endpoint"],
  p256dh: subscriptions["auth_key_1"]["p256dh"],
  auth: subscriptions["auth_key_1"]["auth"],
  vapid: a_hash_including(...)
}
expect(WebPush).to receive(:payload_send).with(first_notification_payload)

Impact

• In a configured deployment, an authenticated user can register an attacker-controlled or otherwise unauthorized HTTPS URL.
• The server then sends outbound POST requests there whenever a notification is pushed.
• This is a stored, mostly blind SSRF primitive: useful for outbound interaction with attacker infrastructure and, where routable, internal HTTPS services.
• Notification metadata is disclosed to the supplied endpoint through the encrypted web push request path.

Patches

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

Workarounds

Disable the push notifications feature by removing the VAPID keys in the server.

Resource

SSRF

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 privileged admin user who can edit an affected landing page can store arbitrary HTML/JavaScript in an HTML block, and the public page renders it with html_safe and no output escaping.

Technical description

This issue lets any admin who can edit an affected landing page store arbitrary HTML and JavaScript in an HTML block. The block is then rendered back through Decidim::ContentBlocks::HtmlCell#html_content without a sanitization boundary, so the script executes later in visitor's browsers.

Impact

• A user with landing-page editing rights for an affected scope can persist JavaScript that executes in visitor's browsers on that page.
• Because exploitation already requires privileged administrative access, the practical risk is lower than a participant-controlled or unauthenticated stored XSS. It still creates a browser-execution primitive in a trusted admin-editable surface.

Patches

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

Workarounds

Do not give admin permissions to non-trustful users.

Reference

Stored XSS

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 normal download_your_data flow requires the requester to be logged in as the export owner, but the resulting Active Storage blob redirect URL can be replayed without authentication by anyone who obtains it.

Technical description

This private export flow turns an authenticated, user-scoped download into a reusable bearer link because the protected Decidim endpoint redirects to the underlying Active Storage blob URL. Decidim::DownloadYourDataController#download_file correctly scopes the export record to current_user, so the wrapper route itself is not directly accessible to another user. However, once the owner performs that authenticated GET request, the response redirects to a signed Active Storage URL that is no longer bound to the user session. Anyone who learns that URL can replay it and retrieve the file without being logged in as the export owner.

Because the blob redirect URL is delivered through a GET request and appears in the redirect chain, it is more likely to leak through browser history, logs, proxy tooling, screenshots, copied links, support transcripts, or other client-side handling of URLs.

Reproduction steps:

Step 1. Generate or locate a completed export in the Web UI.

1. Sign in as user@example.org at http://localhost:3001/users/sign_in.
2. Open http://localhost:3001/download_your_data.
3. Request a new export from the page and wait until the export becomes downloadable.
4. Open the completed export entry from the list and copy its wrapper URL, for example http://localhost:3001/download_your_data/download?uuid=07286e61-932d-46d4-bd74-bcd1340c503f .

Step 2. Download through the authenticated wrapper route.

1. While still signed in as user@example.org, open the wrapper URL in the browser.
2. Confirm that this Decidim route requires the owner session and is not directly usable when logged out or when logged in as another user.

Step 3. Capture the final bearer URL in the redirect chain.

1. In DevTools Network or Burp, inspect the redirect sequence for the wrapper request.
2. Copy the Active Storage redirect URL, typically matching http://localhost:3001/rails/active_storage/blobs/redirect/<SIGNED_ID>/<FILENAME>.
3. Note that the Active Storage redirect URL is no longer protected by the Decidim ownership check.

Step 4. Replay the final file URL without authentication.

1. Open a private window or separate browser with no Decidim session.
2. Paste the copied http://localhost:3001/rails/active_storage/blobs/redirect/<SIGNED_ID>/<FILENAME> URL.
3. Confirm the export file still downloads even though you are not logged in as the export owner.

Impact

Personal data exports can be retrieved through leakage channels such as browser history, logs, referrers, screenshots, copied links, support transcripts, intercepted email content, or other client-side disclosure of the GET URL.

Patches

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

Workarounds

Disable Private Downloads URLs

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 push-subscription endpoint stores an attacker-controlled delivery URL, and the notification send path becomes an outbound-request sink when VAPID delivery is enabled. The practical result is an authenticated, stored, mostly blind SSRF primitive to arbitrary HTTPS endpoints reachable from the app server.

Technical description

When VAPID delivery is enabled, the notification subscription flow stores the client-supplied push endpoint without checking that it belongs to an approved push service. The send path later passes that stored URL to WebPush.payload_send, turning the subscription into an attacker-controlled outbound request destination. This is the source-to-sink chain:

1. Source: attacker-controlled subscription.endpoint in the JSON body posted to POST /notifications_subscriptions.
2. Persistence: params[:endpoint] is stored under user.notification_settings["subscriptions"].
3. Retrieval: user.notifications_subscriptions.values returns that stored endpoint later.
4. Sink: build_payload sets endpoint: subscription["endpoint"].
5. Outbound request: WebPush.payload_send(**payload) uses the attacker-supplied endpoint as the destination.

One spec asserts that the endpoint is persisted exactly as supplied:

# decidim-core/spec/services/decidim/notifications_subscriptions_persistor_spec.rb
expect(user.notifications_subscriptions["auth_code_121"]["endpoint"]).to eq(params[:endpoint])

Another spec asserts that SendPushNotification passes the stored endpoint into WebPush.payload_send:

# decidim-core/spec/services/decidim/send_push_notification_spec.rb
first_notification_payload = {
  message:,
  endpoint: subscriptions["auth_key_1"]["endpoint"],
  p256dh: subscriptions["auth_key_1"]["p256dh"],
  auth: subscriptions["auth_key_1"]["auth"],
  vapid: a_hash_including(...)
}
expect(WebPush).to receive(:payload_send).with(first_notification_payload)

Impact

• In a configured deployment, an authenticated user can register an attacker-controlled or otherwise unauthorized HTTPS URL.
• The server then sends outbound POST requests there whenever a notification is pushed.
• This is a stored, mostly blind SSRF primitive: useful for outbound interaction with attacker infrastructure and, where routable, internal HTTPS services.
• Notification metadata is disclosed to the supplied endpoint through the encrypted web push request path.

Patches

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

Workarounds

Disable the push notifications feature by removing the VAPID keys in the server.

Resource

SSRF

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 privileged admin user who can edit an affected landing page can store arbitrary HTML/JavaScript in an HTML block, and the public page renders it with html_safe and no output escaping.

Technical description

This issue lets any admin who can edit an affected landing page store arbitrary HTML and JavaScript in an HTML block. The block is then rendered back through Decidim::ContentBlocks::HtmlCell#html_content without a sanitization boundary, so the script executes later in visitor's browsers.

Impact

• A user with landing-page editing rights for an affected scope can persist JavaScript that executes in visitor's browsers on that page.
• Because exploitation already requires privileged administrative access, the practical risk is lower than a participant-controlled or unauthenticated stored XSS. It still creates a browser-execution primitive in a trusted admin-editable surface.

Patches

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

Workarounds

Do not give admin permissions to non-trustful users.

Reference

Stored XSS

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 normal download_your_data flow requires the requester to be logged in as the export owner, but the resulting Active Storage blob redirect URL can be replayed without authentication by anyone who obtains it.

Technical description

This private export flow turns an authenticated, user-scoped download into a reusable bearer link because the protected Decidim endpoint redirects to the underlying Active Storage blob URL. Decidim::DownloadYourDataController#download_file correctly scopes the export record to current_user, so the wrapper route itself is not directly accessible to another user. However, once the owner performs that authenticated GET request, the response redirects to a signed Active Storage URL that is no longer bound to the user session. Anyone who learns that URL can replay it and retrieve the file without being logged in as the export owner.

Because the blob redirect URL is delivered through a GET request and appears in the redirect chain, it is more likely to leak through browser history, logs, proxy tooling, screenshots, copied links, support transcripts, or other client-side handling of URLs.

Reproduction steps:

Step 1. Generate or locate a completed export in the Web UI.

1. Sign in as user@example.org at http://localhost:3001/users/sign_in.
2. Open http://localhost:3001/download_your_data.
3. Request a new export from the page and wait until the export becomes downloadable.
4. Open the completed export entry from the list and copy its wrapper URL, for example http://localhost:3001/download_your_data/download?uuid=07286e61-932d-46d4-bd74-bcd1340c503f .

Step 2. Download through the authenticated wrapper route.

1. While still signed in as user@example.org, open the wrapper URL in the browser.
2. Confirm that this Decidim route requires the owner session and is not directly usable when logged out or when logged in as another user.

Step 3. Capture the final bearer URL in the redirect chain.

1. In DevTools Network or Burp, inspect the redirect sequence for the wrapper request.
2. Copy the Active Storage redirect URL, typically matching http://localhost:3001/rails/active_storage/blobs/redirect/<SIGNED_ID>/<FILENAME>.
3. Note that the Active Storage redirect URL is no longer protected by the Decidim ownership check.

Step 4. Replay the final file URL without authentication.

1. Open a private window or separate browser with no Decidim session.
2. Paste the copied http://localhost:3001/rails/active_storage/blobs/redirect/<SIGNED_ID>/<FILENAME> URL.
3. Confirm the export file still downloads even though you are not logged in as the export owner.

Impact

Personal data exports can be retrieved through leakage channels such as browser history, logs, referrers, screenshots, copied links, support transcripts, intercepted email content, or other client-side disclosure of the GET URL.

Patches

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

Workarounds

Disable Private Downloads URLs

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 push-subscription endpoint stores an attacker-controlled delivery URL, and the notification send path becomes an outbound-request sink when VAPID delivery is enabled. The practical result is an authenticated, stored, mostly blind SSRF primitive to arbitrary HTTPS endpoints reachable from the app server.

Technical description

When VAPID delivery is enabled, the notification subscription flow stores the client-supplied push endpoint without checking that it belongs to an approved push service. The send path later passes that stored URL to WebPush.payload_send, turning the subscription into an attacker-controlled outbound request destination. This is the source-to-sink chain:

1. Source: attacker-controlled subscription.endpoint in the JSON body posted to POST /notifications_subscriptions.
2. Persistence: params[:endpoint] is stored under user.notification_settings["subscriptions"].
3. Retrieval: user.notifications_subscriptions.values returns that stored endpoint later.
4. Sink: build_payload sets endpoint: subscription["endpoint"].
5. Outbound request: WebPush.payload_send(**payload) uses the attacker-supplied endpoint as the destination.

One spec asserts that the endpoint is persisted exactly as supplied:

# decidim-core/spec/services/decidim/notifications_subscriptions_persistor_spec.rb
expect(user.notifications_subscriptions["auth_code_121"]["endpoint"]).to eq(params[:endpoint])

Another spec asserts that SendPushNotification passes the stored endpoint into WebPush.payload_send:

# decidim-core/spec/services/decidim/send_push_notification_spec.rb
first_notification_payload = {
  message:,
  endpoint: subscriptions["auth_key_1"]["endpoint"],
  p256dh: subscriptions["auth_key_1"]["p256dh"],
  auth: subscriptions["auth_key_1"]["auth"],
  vapid: a_hash_including(...)
}
expect(WebPush).to receive(:payload_send).with(first_notification_payload)

Impact

• In a configured deployment, an authenticated user can register an attacker-controlled or otherwise unauthorized HTTPS URL.
• The server then sends outbound POST requests there whenever a notification is pushed.
• This is a stored, mostly blind SSRF primitive: useful for outbound interaction with attacker infrastructure and, where routable, internal HTTPS services.
• Notification metadata is disclosed to the supplied endpoint through the encrypted web push request path.

Patches

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

Workarounds

Disable the push notifications feature by removing the VAPID keys in the server.

Resource

SSRF

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 privileged admin user who can edit an affected landing page can store arbitrary HTML/JavaScript in an HTML block, and the public page renders it with html_safe and no output escaping.

Technical description

This issue lets any admin who can edit an affected landing page store arbitrary HTML and JavaScript in an HTML block. The block is then rendered back through Decidim::ContentBlocks::HtmlCell#html_content without a sanitization boundary, so the script executes later in visitor's browsers.

Impact

• A user with landing-page editing rights for an affected scope can persist JavaScript that executes in visitor's browsers on that page.
• Because exploitation already requires privileged administrative access, the practical risk is lower than a participant-controlled or unauthenticated stored XSS. It still creates a browser-execution primitive in a trusted admin-editable surface.

Patches

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

Workarounds

Do not give admin permissions to non-trustful users.

Reference

Stored XSS

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 normal download_your_data flow requires the requester to be logged in as the export owner, but the resulting Active Storage blob redirect URL can be replayed without authentication by anyone who obtains it.

Technical description

This private export flow turns an authenticated, user-scoped download into a reusable bearer link because the protected Decidim endpoint redirects to the underlying Active Storage blob URL. Decidim::DownloadYourDataController#download_file correctly scopes the export record to current_user, so the wrapper route itself is not directly accessible to another user. However, once the owner performs that authenticated GET request, the response redirects to a signed Active Storage URL that is no longer bound to the user session. Anyone who learns that URL can replay it and retrieve the file without being logged in as the export owner.

Because the blob redirect URL is delivered through a GET request and appears in the redirect chain, it is more likely to leak through browser history, logs, proxy tooling, screenshots, copied links, support transcripts, or other client-side handling of URLs.

Reproduction steps:

Step 1. Generate or locate a completed export in the Web UI.

1. Sign in as user@example.org at http://localhost:3001/users/sign_in.
2. Open http://localhost:3001/download_your_data.
3. Request a new export from the page and wait until the export becomes downloadable.
4. Open the completed export entry from the list and copy its wrapper URL, for example http://localhost:3001/download_your_data/download?uuid=07286e61-932d-46d4-bd74-bcd1340c503f .

Step 2. Download through the authenticated wrapper route.

1. While still signed in as user@example.org, open the wrapper URL in the browser.
2. Confirm that this Decidim route requires the owner session and is not directly usable when logged out or when logged in as another user.

Step 3. Capture the final bearer URL in the redirect chain.

1. In DevTools Network or Burp, inspect the redirect sequence for the wrapper request.
2. Copy the Active Storage redirect URL, typically matching http://localhost:3001/rails/active_storage/blobs/redirect/<SIGNED_ID>/<FILENAME>.
3. Note that the Active Storage redirect URL is no longer protected by the Decidim ownership check.

Step 4. Replay the final file URL without authentication.

1. Open a private window or separate browser with no Decidim session.
2. Paste the copied http://localhost:3001/rails/active_storage/blobs/redirect/<SIGNED_ID>/<FILENAME> URL.
3. Confirm the export file still downloads even though you are not logged in as the export owner.

Impact

Personal data exports can be retrieved through leakage channels such as browser history, logs, referrers, screenshots, copied links, support transcripts, intercepted email content, or other client-side disclosure of the GET URL.

Patches

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

Workarounds

Disable Private Downloads URLs

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.