AzuraCast has Password Reset Poisoning via Untrusted X-Forwarded-Host Header that Leads to Account Takeover and 2FA Bypass

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-42606: 0.48% estimated exploitation activity in the next 30 days; percentile 41.20 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The ApplyXForwarded middleware unconditionally trusts the client-supplied X-Forwarded-Host HTTP header with no trusted proxy allowlist. An unauthenticated attacker can poison the password reset URL sent to any user by injecting this header when triggering the forgot-password flow. When the victim clicks the poisoned link, their reset token is exfiltrated to the attacker's server. The attacker then uses the token on the real instance to reset the victim's password and destroy their 2FA configuration, achieving full account takeover. Details Root Cause 1: Unconditional X-Forwarded-Host Trust backend/src/Middleware/ApplyXForwarded.php:35-40: There is no validation that the request originates from a trusted reverse proxy. Any direct client can set this header and it will be accepted. In the default Docker deployment, nginx's PHP location block (util/docker/web/nginx/azuracast.conf.tmpl:150-171) uses fastcgipass with include fastcgiparams. Standard nginx behavior passes all client…

Published by the source

4 May 2026, 21:17 UTC

Last modified by the source

13 May 2026, 13:42 UTC

Source last checked

26 Oct 2026, 14:40 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-gv7r-3mr9-h5x8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-42606

Advisory: AzuraCast has Password Reset Poisoning via Untrusted X-Forwarded-Host Header that Leads to Account Takeover and 2FA Bypass
IDs: CVE-2026-42606, GHSA-gv7r-3mr9-h5x8
Record: https://patchnext.com/advisories/cve-2026-42606 (revision 1, source checked 26 Oct 2026, 14:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: azuracast/azuracast 0.23.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist azuracast/azuracast: affected <= 0.23.5; fixed in 0.23.6

## Suggested inspection (read-only)
- Packagist azuracast/azuracast: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on azuracast/azuracast.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gv7r-3mr9-h5x8 (GitHub-reviewed advisory GHSA-gv7r-3mr9-h5x8 lists affected ranges: Packagist azuracast/azuracast >=0 <=0.23.5)

Commands are suggestions: review each one before running it.