Security Resilience

CVE-2025-53373

Auth Bypass

Auth Bypass
Published
07 July 2025
Modified
17 June 2026
CVSS Score v4 8.9
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0034 26th percentile
Risk Priority 44 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-53373 is a high-severity Weak Password Recovery Mechanism for Forgotten Password (CWE-640) vulnerability. Its CVSS base score is 8.9 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Valid Accounts (T1078); ranked at the 26th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to IA-12 (Identity Proofing) and IA-5 (Authenticator Management) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A07:2025 Authentication Failures

EU & UK References

Vulnerability Data

Natours is a Tour Booking API. The attacker can easily take over any victim account by injecting an attacker-controlled server domain in the Host header when requesting the /forgetpassword endpoint. This vulnerability is fixed with commit 7401793a8d9ed0f0c250c4e0ee2815d685d7a70b.

CWE(s)
CWE-640

Related Threats

MITRE ATT&CK Enterprise Techniques

T1078 Valid Accounts Stealth
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
attack.mitre.org →
T1078.004 Cloud Accounts Stealth
Valid accounts in cloud environments may allow adversaries to perform actions to achieve Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
attack.mitre.org →
T1586 Compromise Accounts Resource Development
Adversaries may compromise accounts with services that can be used during targeting.
attack.mitre.org →
T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-38468Shared CWE-640
CVE-2026-90522Shared CWE-640
CVE-2026-80196Shared CWE-640
CVE-2017-7615Shared CWE-640
CVE-2024-9302Shared CWE-640
CVE-2023-7264Shared CWE-640
CVE-2025-43932Shared CWE-640
CVE-2024-42915Shared CWE-640
CVE-2026-9609Shared CWE-640
CVE-2024-6125Shared CWE-640

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

IA-12 Identity Proofing good match

Identity proofing at appropriate assurance levels ensures forgotten-password recovery cannot succeed without strong verification of the user.

IA-5 Authenticator Management good match

Authenticator management requires secure distribution, reset, and verification procedures that directly address weak password recovery flows.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-01 mostly match
blocks

Credential lifecycle management directly includes password reset/recovery flows.

PR.AA-02 mostly match
blocks

Identity proofing is the core control that prevents weak or bypassed recovery mechanisms.

PR.AA-03 partial match
blocks

Authentication policy covers strength/MFA but does not address recovery path weaknesses.

PR.PS-06 partial match
blocks

Secure SDLC reduces implementation flaws but is not specific to password-recovery design.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.28 Secure coding partial match
prevents

Secure-coding standards can prevent weak recovery implementations, yet the control is wider in scope.

References