NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

wallabag/wallabag Has Multiple Cross-Site Request Forgery (CSRF) VulnerabilitiesGHSA-5pm7-cp8f-p2c2

MEDIUMFix: wallabag/wallabag@edffef8

GHSA-5pm7-cp8f-p2c2 is a medium-severity (CVSS 4.3) vulnerability in wallabag/wallabag. A fix is available for wallabag/wallabag — see the affected versions and patch details below.

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Apr 9, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐘wallabag/wallabag

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

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.

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

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistwallabag/wallabagall versions2.6.11composer require wallabag/wallabag:^2.6.11

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wallabag/wallabag, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update wallabag/wallabag to 2.6.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5pm7-cp8f-p2c2 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

## Impact 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
O3 Security · Impact-Aware SCA

Is GHSA-5pm7-cp8f-p2c2 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
wallabag/wallabag Has Multiple Cross-Site Request…