GHSA-5PM7-CP8F-P2C2

Resolution

These vulnerabilities have been addressed in wallabag version 2.6.11. The affected endpoints have been modified to require the HTTP POST method along with a valid CSRF token for state-changing actions, preventing attackers from forcing users' browsers to perform these actions unintentionally.

Credits

Found, reported and fixed by @yguedidi

wallabag versions prior to 2.6.11 were discovered to contain multiple Cross-Site Request Forgery (CSRF) vulnerabilities across several endpoints. An attacker could craft a malicious link or page that, if visited by a logged-in wallabag user, could trick the user's browser into performing unintended actions within their wallabag account without their consent. Additionally, one endpoint affects the login page locale setting.

The affected endpoints allow attackers to potentially perform actions such as:

• Manage API Tokens:
  • /generate-token
  • /revoke-token
• Manage User Rules:
  • /tagging-rule/delete/{taggingRule}
  • /ignore-origin-user-rule/delete/{ignoreOriginUserRule}
• Modify User Configuration:
  • /config/view-mode
• Manage Individual Entries:
  • /reload/{id}
  • /archive/{id}
  • /star/{id}
  • /delete/{id}
  • /share/{id}
  • /share/delete/{id}
• Manage Tags:
  • /remove-tag/{entry}/{tag}
  • /tag/search/{filter}
  • /tag/delete/{slug}
• Perform Bulk Actions:
  • /mass
• Change Interface Language (Login Page):
  • /locale/{language}

Successfully exploiting these vulnerabilities could lead to unauthorized modification or deletion of user data, configuration changes, token manipulation, or interface changes, depending on the specific endpoint targeted.

This set of vulnerabilities has an aggregated CVSS v3.1 score of 4.3 (Medium).

Users are strongly advised to upgrade their wallabag instance to version 2.6.11 or later to mitigate these vulnerabilities.

A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.

GHSA-5PM7-CP8F-P2C2 has a CVSS score of 4.3 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.6.11); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is GHSA-5PM7-CP8F-P2C2? GHSA-5PM7-CP8F-P2C2 is a medium-severity cross-site request forgery (CSRF) vulnerability in wallabag/wallabag (composer), affecting versions < 2.6.11. It is fixed in 2.6.11. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
2. How severe is GHSA-5PM7-CP8F-P2C2? GHSA-5PM7-CP8F-P2C2 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of wallabag/wallabag are affected by GHSA-5PM7-CP8F-P2C2? wallabag/wallabag (composer) versions < 2.6.11 is affected.
4. Is there a fix for GHSA-5PM7-CP8F-P2C2? Yes. GHSA-5PM7-CP8F-P2C2 is fixed in 2.6.11. Upgrade to this version or later.
5. Is GHSA-5PM7-CP8F-P2C2 exploitable, and should I be worried? Whether GHSA-5PM7-CP8F-P2C2 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-5PM7-CP8F-P2C2 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-5PM7-CP8F-P2C2? Upgrade wallabag/wallabag to 2.6.11 or later.