Forced logout via missing CSRF token validation
Published Feb 6, 2025 · Updated Feb 6, 2025
Cross-site request forgery in the QloApps 1.6.1 front-office logout handler allows remote attackers to terminate authenticated user sessions. The mylogout URL accepts a cross-site GET request without validating a CSRF token and immediately destroys the active session. Exploitation requires an authenticated user to load attacker-controlled content; the demonstrated consequence is forced logout and session interruption only.
Summary
What happened
Cross-site request forgery in the QloApps 1.6.1 front-office logout handler allows remote attackers to terminate authenticated user sessions. The mylogout URL accepts a cross-site GET request without validating a CSRF token and immediately destroys the active session. Exploitation requires an authenticated user to load attacker-controlled content; the demonstrated consequence is forced logout and session interruption only.
The record
- CVE
- CVE-2025-1074
- Published
- Feb 6, 2025
- Updated
- Feb 6, 2025
- Vendor
- Bagisto
- Product
- QloApps
- Classifications
- CWE-862, CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 6, 2025CVE publishedPublication date reported by the CVE source.
- Feb 6, 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=1.6.1
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
- QloApps CSRF logout proof of conceptproof of concept · demonstrated
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