CVE-2025-43933: n/a
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 7 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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-26.
What to do
AI-suggested
To mitigate this vulnerability, organizations should immediately ensure that the SERVER_NAME parameter is correctly configured on their web servers to a fixed, trusted domain name. This prevents the application from relying on the Host HTTP header for security-sensitive operations like password resets. Developers should implement strict validation and sanitization of the Host header and avoid using it for authentication or authorization decisions. Additionally, password reset tokens should be bound to the intended domain and include mechanisms such as token expiration, single-use enforcement, and multi-factor authentication to reduce the risk of misuse. Organizations should audit their web applications for similar misconfigurations and review password reset workflows for security weaknesses. Monitoring and logging of password reset requests and anomalies in Host headers can help detect exploitation attempts. Finally, applying any vendor patches or updates addressing this issue as soon as they become available is critical.
Description
fblog through 983bede allows account takeover via the password reset feature because SERVER_NAME is not configured and thus a reset depends on the Host HTTP header.