CVE-2026-25858
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedmacrozheng 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 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencemacrozheng mall version 1.0.3 and prior has an authentication bypass in the mall-portal password reset workflow. The one-time password (OTP) is exposed directly in the API response, and the system validates password reset requests solely by comparing the provided OTP to the value stored by telephone number, without verifying user identity or ownership of the telephone number. This allows unauthenticated attackers to reset any user's password using only the victim's telephone number.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.0.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed version of macrozheng mallLocate the mall-portal module and check its version identifier in build configuration files (pom.xml), application properties, or the compiled WAR/JAR manifestAffected if version is 1.0.3 or lower
-
Verify mall-portal module is deployed and accessibleConfirm the mall-portal web application is running and the password reset endpoint is reachable via HTTP/HTTPSAffected if mall-portal module is exposed and accepting requests
-
Confirm password reset endpoint does not require prior authenticationSend a password reset request (such as sending a verification code to a phone number) without providing any session token or existing login credentialsAffected if the request succeeds without requiring an authenticated session
-
Check if OTP is exposed in the password reset API responseCapture the HTTP response from the password reset or OTP sending endpoint and inspect whether the one-time password or verification code is returned in the response body or headersAffected if the OTP value appears in the API response
-
Verify password reset only validates OTP-to-phone matchingTest the password reset flow by providing a valid OTP paired with a phone number, without additional identity verification steps such as email confirmation, security questions, or existing session verificationAffected if the password can be changed using only OTP and phone number without proving identity ownership
A user is affected if running macrozheng mall version 1.0.3 or lower where the mall-portal password reset endpoint is exposed, unauthenticated, and returns the OTP in the API response without requiring identity verification beyond OTP-to-phone matching.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediate mitigation requires disabling the vulnerable password reset endpoint or adding proper identity verification (e.g., email verification, security questions, or multi-factor authentication) before allowing password resets, and ensuring OTPs are not exposed in API responses.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25858 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-25858 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data