wallabag 2 through 2.6.14 allows SSRF because a crafted title or content field is mishandled during PDF export.

A vulnerability was found in wallabag 2.5.4. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the file /config of the component Profile Config. The manipulation of the argument Name leads to allocation of resources. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-233359. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Improper Authorization in GitHub repository wallabag/wallabag prior to 2.5.3.

Improper Authorization in GitHub repository wallabag/wallabag prior to 2.5.3.

Cross-Site Request Forgery (CSRF) in GitHub repository wallabag/wallabag prior to 2.5.4.

Cross-site Scripting (XSS) - Stored in GitHub repository wallabag/wallabag prior to 2.5.4.

Improper Authorization in GitHub repository wallabag/wallabag prior to 2.5.4.

Description

wallabag was discovered to contain a Cross-Site Request Forgery (CSRF) which allows attackers to arbitrarily reset annotations, entries and tags, by the GET request to /reset/annotations, /reset/entries, /reset/tags, /reset/archived.

This vulnerability has a CVSSv3.1 score of 4.3.

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

These actions are now doable only via POST method, which ensures that we can't do them via a 3rd-party website.

Credits

We would like to thank @zpbrent for reporting this issue through huntr.dev.

Reference: https://huntr.dev/bounties/4ee0ef74-e4d4-46e7-a05c-076bce522299/

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/

wallabag version 2.5.2 contains a Cross-Site Request Forgery (CSRF) vulnerability that allows attackers to arbitrarily delete user accounts via the /account/delete endpoint. This issue is fixed in version 2.5.4.

The Wallabag application 2.2.3 to 2.3.2 is affected by one cross-site scripting (XSS) vulnerability that is stored within the configuration page. This vulnerability enables the execution of a JavaScript payload each time an administrator visits the configuration page. The vulnerability can be exploited with authentication and used to target administrators and steal their sessions.