Cyber Resilience

CVE-2026-25858

Auth Bypass in Macrozheng Mall ≤ 1.0.3

Public PoCAuth Bypass
Published
07 February 2026
Modified
14 July 2026
CVSS Score v4 9.3
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:N/SC:N/SI:N/SA:N/E:X/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.0062 46th percentile
Risk Priority 46 floored blend · peak EPSS

Summary

CVE-2026-25858 is a critical-severity Weak Password Recovery Mechanism for Forgotten Password (CWE-640) vulnerability in Macrozheng Mall. Its CVSS base score is 9.3 (Critical).

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

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.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-25858 is an authentication vulnerability (CWE-640) in macrozheng mall version 1.0.3 and prior, specifically within the mall-portal password reset workflow. The flaw stems from the password reset process exposing the one-time password (OTP) directly in the API response and validating reset requests only by comparing the provided OTP against a value stored by telephone number, without any verification of user identity or telephone number ownership. This enables unauthenticated attackers to reset arbitrary user passwords using just a victim's telephone number, which may be known or guessable. The vulnerability carries a CVSS v3.1 base score of 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).

An unauthenticated attacker with network access can exploit this vulnerability remotely and with low complexity. By obtaining a victim's telephone number, the attacker triggers the password reset flow to retrieve the OTP from the API response, then submits it along with a new password to complete the reset. This results in full account takeover, granting high-impact access to the victim's confidentiality and integrity, such as reading sensitive data or modifying account settings.

Mitigation details are available in related advisories, including the GitHub issue tracker at https://github.com/macrozheng/mall/issues/946, the project website at https://www.macrozheng.com/, and the VulnCheck advisory at https://www.vulncheck.com/advisories/macrozheng-mall-unauthenticated-password-reset-via-otp-disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

macrozheng mall version 1.0.3 and prior contains an authentication vulnerability in the mall-portal password reset workflow that allows an unauthenticated attacker to reset arbitrary user account passwords using only a victim’s telephone number. The password reset flow exposes the one-time…

more

password (OTP) directly in the API response and validates password reset requests solely by comparing the provided OTP to a value stored by telephone number, without verifying user identity or ownership of the telephone number. This enables remote account takeover of any user with a known or guessable telephone number.

CWE(s)

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.
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.
T1110.001 Password Guessing Credential Access
Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-8742Same product: Macrozheng Mall
CVE-2025-9514Same product: Macrozheng Mall
CVE-2025-15118Same product: Macrozheng Mall
CVE-2025-13443Same product: Macrozheng Mall
CVE-2025-9836Same product: Macrozheng Mall
CVE-2025-8755Same product: Macrozheng Mall
CVE-2025-8750Same product: Macrozheng Mall
CVE-2024-11619Same product: Macrozheng Mall
CVE-2025-9835Same product: Macrozheng Mall
CVE-2025-8191Same product: Macrozheng Mall

Affected Assets

macrozheng
mall
≤ 1.0.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V7.4.3

Mitigating Controls (NIST 800-53 r5) AI

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

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
prevents

Credential lifecycle management directly includes password reset/recovery flows.

PR.AA-02 mostly match
prevents

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

PR.AA-03 partial match
prevents

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

PR.PS-06 partial match
prevents

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.

degrades

Strong authentication-information lifecycle rules directly address weak password-recovery flows.

prevents

Secure-SDLC practices can embed strong recovery design, yet the control is broader than this single weakness.

prevents

Application-security requirements can mandate secure recovery flows, but the control covers many other requirements.

prevents

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

mitigates

Secure-authentication requirements include robust forgotten-password procedures.

none

Proper access-rights provisioning can limit who can trigger recovery, but does not fix the recovery mechanism itself.

References