wallabag 2.3.3 before 2.6.16 contains a stored cross-site scripting vulnerability that allows unauthenticated attackers to inject scripts through article author metadata rendered with Twig raw in entry.html.twig. Attackers can embed HTML event handlers in a web page's author metadata so scripts run in a victim's wallabag session when the saved entry is opened, exposing their data.
wallabag 2.6.13 through 2.6.14 contains a stored cross-site scripting vulnerability that allows authenticated users to host arbitrary HTML by triggering a failed Pocket HTML, Pocket CSV or Shaarli import. Attackers can upload an HTML file with script but no anchor elements, leaving it at the predictable /uploads/import/<user-id>.html path to execute script in victims' wallabag sessions.
wallabag 2 through 2.6.14 allows SSRF because a crafted title or content field is mishandled during PDF export.
CSRF leading to delete account in wallabag/wallabag
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/
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/
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.4.
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.
Description
The export feature lets a user export a single entry or a set of entries in a given format (e.g. PDF, MOBI, TXT).
For example, https://yourinstance.wallabag.org/export/45.pdf will export the entry with id 45 in PDF format.
Since wallabag 2.0.0-alpha.1, this feature is vulnerable to an insecure direct object reference attack. A logged user can export any single entry without ownership validation.
This is due to a lack of access validation in the downloadEntryAction method.
You should immediately patch your instance to version 2.5.3 or higher if you have more than one user and/or having open registration.
Resolution
A user check is now done in the vulnerable method before sending the exported entry.
The Entry retrieval through a ParamConverter has also been replaced with a call to the EntryRepository in order to prevent any information disclosure through response discrepancy.
Workaround
If you are unable to update to the latest version or if you want to temporarily limit risk of exploitation, you may consider blocking requests to the endpoint /export/.
E.g. with nginx:
nginx location /export { deny all; }
Credits
We would like to thank @bAuh0lz for reporting this issue through huntr.dev.
Reference: https://www.huntr.dev/bounties/3adef66f-fc86-4e6d-a540-2ffa59342ff0/
Impact The annotations feature lets users add annotations on highlighted parts of an entry.
The controller does not validate authorization on PUT and DELETE requests which lets a logged user modify or delete any annotation using their ID on their endpoints example.org/annotations/{id}.
These vulnerable requests also disclose highlighted parts of the entry to the attacker.
You should immediately patch your instance to version 2.5.3 or higher if you have more than one user and/or having open registration.
Resolution
A user check is now done in the vulnerable methods before applying change on an annotation.
The Annotation retrieval through a ParamConverter has also been replaced with a call to the AnnotationRepository in order to prevent any information disclosure through response discrepancy.
Workarounds
Credits
We would like to thank @bAuh0lz for reporting this issue through huntr.dev.
Reference: https://huntr.dev/bounties/8fdd9b31-d89b-4bbe-9557-20b960faf926/
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.