API client deletion via unprotected GET request
Published Aug 21, 2023 · Updated Oct 3, 2024
Cross-site request forgery in wallabag before 2.6.3 allows remote attackers to delete a user's API client through a crafted request. DeveloperController's client-deletion route accepts a state-changing GET request without validating a CSRF token, allowing a third-party page to invoke the action. A logged-in wallabag user must visit attacker-controlled content, and the deletion remains limited to an API client owned by that user.
Summary
What happened
Cross-site request forgery in wallabag before 2.6.3 allows remote attackers to delete a user's API client through a crafted request. DeveloperController's client-deletion route accepts a state-changing GET request without validating a CSRF token, allowing a third-party page to invoke the action. A logged-in wallabag user must visit attacker-controlled content, and the deletion remains limited to an API client owned by that user.
The record
- CVE
- CVE-2023-4455
- Published
- Aug 21, 2023
- Updated
- Oct 3, 2024
- Vendor
- wallabag
- Product
- wallabag
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 21, 2023CVE publishedPublication date reported by the CVE source.
- Oct 3, 2024Record 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=0 <2.6.3
- Affected versionversion=unspecified <2.6.3
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
- huntr.dev CSRF proof of conceptproof of concept · unverified
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