Skip to main content
CVE-2025-43931VulnerabilityPublished Updated

CVE-2025-43931: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

AI-suggested

To mitigate CVE-2025-43931, organizations should immediately configure the SERVER_NAME parameter in their Flask applications to a fixed, trusted domain name. This ensures that password reset links are generated with a consistent and secure domain, preventing Host header manipulation. Additionally, implement strict validation of the Host header and consider using HTTPS with HSTS to prevent man-in-the-middle attacks. Review and enhance password reset workflows by incorporating multi-factor authentication (MFA) for sensitive account changes. Monitor logs for unusual password reset requests or anomalies in Host headers. If possible, apply any available patches or updates from flask-boilerplate maintainers as soon as they are released. Conduct security testing focused on password recovery mechanisms to identify similar weaknesses. Educate developers on secure configuration practices to avoid reliance on user-controllable headers for security-critical functions.

Description

flask-boilerplate through a170e7c allows account takeover via the password reset feature because SERVER_NAME is not configured and thus a reset depends on the Host HTTP header.

References

Community reviews

Loading reviews…