Account takeover via predictable password reset tokens
Published Sep 28, 2022 · Updated May 21, 2025
Authorization bypass in b2evolution before 7.2.5 allows remote attackers to take over arbitrary accounts via password-reset tokens. The password-reset token generator uses predictable pseudorandom output instead of cryptographically secure randomness. The reset flow is reachable without authentication in a default installation; a predicted token yields a valid victim session and permits password replacement.
Summary
What happened
Authorization bypass in b2evolution before 7.2.5 allows remote attackers to take over arbitrary accounts via password-reset tokens. The password-reset token generator uses predictable pseudorandom output instead of cryptographically secure randomness. The reset flow is reachable without authentication in a default installation; a predicted token yields a valid victim session and permits password replacement.
The record
- CVE
- CVE-2022-30935
- Published
- Sep 28, 2022
- Updated
- May 21, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-330, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 28, 2022CVE publishedPublication date reported by the CVE source.
- May 21, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo