Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-15689 – Password Reset Link Poisoning / Account Takeover – Dancer2::Plugin::Auth::Extensibl

Be the first to know when new zero-days emerge:

Summary

CVE-2026-15689 is a host header injection vulnerability (CWE-640: Weak Password Recovery Mechanism) in Dancer2::Plugin::Auth::Extensible, a Perl authentication plugin for the Dancer2 web framework. Affected versions build password reset and welcome emails using the untrusted request Host header, allowing an unauthenticated attacker to poison the reset link and take over any user account. The issue carries a CRITICAL CVSS v3.1 score of 9.8.

Technical details

  • Root cause: the _default_email_password_reset and _default_welcome_send handlers build the link authority from request->base / request->uri_base, which derive from the client-supplied Host header (or X-Forwarded-Host when behind_proxy is enabled) rather than a trusted, configured application hostname.
  • Trigger condition: an unauthenticated POST to /login with submit_reset and a target username generates a fresh reset code for that account and emails a reset link to a host chosen by the attacker; the same code path is triggered by the welcome email when create_user is called with email_welcome set.
  • Attack vector: network, no authentication or user interaction beyond the victim clicking the received (poisoned) link.
  • Impact: if the victim follows the link, the working reset code is delivered to the attacker-controlled host, enabling full account takeover, including high confidentiality, integrity, and availability impact.

Affected software

  • Dancer2::Plugin::Auth::Extensible versions 0 through 0.713 (through 0.711 the code read request->uri_base/request->base directly with no mitigation; 0.712 introduced a uri_base configuration key that defaults to the untrusted value when left unset).

Severity

  • CVSS v3.1 Base Score: 9.8 (CRITICAL)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: upgrade to Dancer2::Plugin::Auth::Extensible 0.713 or later, and explicitly set the uri_base configuration key to the application’s own trusted base URL.
  • If patching is not immediately possible: reject or normalize any request whose Host (or X-Forwarded-Host) does not match an expected application hostname at the web server or reverse proxy layer before it reaches the application.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • server response header: Perl Dancer (with version)
  • x-powered-by response header: Perl Dancer (with version)

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge