Forced logout via cross-site request forgery
Published Feb 27, 2025 · Updated Feb 27, 2025
Cross-site request forgery in pb-cms 2.0 Logout allows remote attackers to terminate a user's authenticated session via a crafted request. The published record does not identify the affected route or disclose how the Logout component accepts the forged request without verifying user intent. A victim with an active session must interact with attacker-controlled content, after which the session ends without the victim choosing to log out.
Summary
What happened
Cross-site request forgery in pb-cms 2.0 Logout allows remote attackers to terminate a user's authenticated session via a crafted request. The published record does not identify the affected route or disclose how the Logout component accepts the forged request without verifying user intent. A victim with an active session must interact with attacker-controlled content, after which the session ends without the victim choosing to log out.
The record
- CVE
- CVE-2025-1745
- Published
- Feb 27, 2025
- Updated
- Feb 27, 2025
- Vendor
- LinZhaoguan
- Product
- pb-cms
- Classifications
- CWE-352, CWE-862
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 27, 2025CVE publishedPublication date reported by the CVE source.
- Feb 27, 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=2.0
What conditions does exploitation require?
What is affected?
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