Skip to main content
CVE-2025-43930VulnerabilityPublished Updated

CVE-2025-43930: hashview · n/a

Affects hashviewSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% 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-26.

What to do

Affected software

ProductAffectedFixed in
GitHubhashview/hashviewpkg:github/hashview/hashviewOther threatsAffected
  • =0.8.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-43930, European organizations should immediately verify and configure the SERVER_NAME parameter correctly on their Hashview servers to ensure that password reset links are generated using a trusted and fixed domain name rather than the Host HTTP header. This prevents attackers from manipulating the reset URL. Additionally, organizations should implement strict validation of incoming HTTP headers and consider employing web application firewalls (WAFs) to detect and block suspicious Host header manipulations. Monitoring password reset requests for anomalies and rate limiting such requests can reduce exploitation risk. Until an official patch is released, organizations should consider disabling the password reset feature or restricting it to verified IP ranges or authenticated sessions. Regularly auditing and updating Hashview to newer versions once patches become available is critical. Finally, organizations should educate users about phishing risks related to password resets and enforce multi-factor authentication (MFA) to reduce the impact of compromised credentials.

Description

Hashview 0.8.1 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…