Second-factor rate-limit bypass via extended session expiry
Published Sep 4, 2025 · Updated Sep 5, 2025
Insufficient session expiration in Weblate before 5.13.1 allows remote authenticated users to bypass second-factor rate limiting. The adjust_session_expiry function assigned password-authenticated users the long authenticated-session lifetime before OTP verification instead of a brief 2FA lifetime. A valid password and enabled second factor are required; the prolonged pre-verification session permits repeated OTP guesses across normal rate-limit windows.
Summary
What happened
Insufficient session expiration in Weblate before 5.13.1 allows remote authenticated users to bypass second-factor rate limiting. The adjust_session_expiry function assigned password-authenticated users the long authenticated-session lifetime before OTP verification instead of a brief 2FA lifetime. A valid password and enabled second factor are required; the prolonged pre-verification session permits repeated OTP guesses across normal rate-limit windows.
The record
- CVE
- CVE-2025-58352
- Published
- Sep 4, 2025
- Updated
- Sep 5, 2025
- Vendor
- Weblate
- Product
- Weblate
- Classifications
- CWE-613, T1110
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 4, 2025CVE publishedPublication date reported by the CVE source.
- Sep 5, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 5.13.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
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