CVE-2023-4455: Wallabag user can delete own API client unintentionally
Description wallabag was discovered to contain a Cross-Site Request Forgery (CSRF) which allows attackers to arbitrarily delete API key via /developer/client/delete/{id}
This vulnerability has a CVSSv3.1 score of 6.5.
You should immediately patch your instance to version 2.6.3 or higher if you have more than one user and/or having open registration.
Resolution
This action is now doable only via POST method, which ensures that we can't do it via a 3rd-party website.
Credits
We would like to thank @tht1997 for reporting this issue through huntr.dev.
Reference: https://huntr.dev/bounties/5ab1b206-5fe8-4737-b275-d705e76f193a/
Other sources
Cross-Site Request Forgery (CSRF) in GitHub repository wallabag/wallabag prior to 2.6.3.
— MITRE
Wallabag user can delete own API client unintentionally
— Packagist
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/wallabag/wallabagto a version that resolves this vulnerability.Fixed in 2.6.3 - Upgrade
Upgrade
wallabag/wallabagto a version that resolves this vulnerability.Fixed in 2.6.3
Event History
Frequently Asked Questions
What is the vulnerability ID of this vulnerability?
The vulnerability ID of this vulnerability is CVE-2023-4455.
What is the title of this vulnerability?
The title of this vulnerability is Cross-Site Request Forgery (CSRF) in GitHub repository wallabag/wallabag prior to 2.6.3.
What is the severity of CVE-2023-4455?
CVE-2023-4455 has a severity score of 6.5, which is medium.
How can I fix this vulnerability?
To fix this vulnerability, you should immediately patch your instance of wallabag to version 2.6.3 or higher.
Where can I find more information about this vulnerability?
You can find more information about this vulnerability on the GitHub commit page and the Wallabag security advisories page.