CVE-2025-43932: JobCenter · Weak Password Recovery
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 13:47 UTC
- 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: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 26 Oct 2026.
What to do
AI-suggested
Immediate mitigation steps include configuring the SERVER_NAME parameter correctly in the JobCenter application to ensure password reset links are generated using a trusted and fixed hostname rather than the Host HTTP header. Organizations should audit their web server and application configurations to verify SERVER_NAME is set and enforced. Implementing strict validation and sanitization of HTTP headers, particularly the Host header, can reduce the risk of header injection or manipulation attacks. Monitoring and logging password reset requests for anomalous patterns can help detect exploitation attempts. Until an official patch is released, consider restricting access to the password reset functionality via network controls or multi-factor authentication to reduce risk. Organizations should also review user account privileges and enforce strong authentication policies. Finally, stay alert for vendor advisories and apply patches promptly once available.
Description
JobCenter through 7e7b0b2 allows account takeover via the password reset feature because SERVER_NAME is not configured and thus a reset depends on the Host HTTP header.