Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

GHSA-56fm-hfp3-x3w3 wallabag/wallabag

MEDIUMFix: wallabag/wallabag@0cfdddc

GHSA-56fm-hfp3-x3w3 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.

Wallabag user can disable 2FA unintentionally

Published
Oct 2, 2023
Updated
Dec 7, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Dec 7, 2024 · 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 was discovered to contain a Cross-Site Request Forgery (CSRF) which allows attackers to arbitrarily disable 2FA through /config/otp/app/disable and /config/otp/email/disable.

This vulnerability has a CVSSv3.1 score of 4.3.

You should upgrade your instance to version 2.6.7 or higher.

Resolution

These endpoints now require POST method.

Credits

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

Reference: https://huntr.dev/bounties/4c446fe7-2a44-4907-b0cf-4ab77d75c487/

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistwallabag/wallabag2.0.0-alpha.1&&< 2.6.72.6.7composer require wallabag/wallabag:^2.6.7

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.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-56fm-hfp3-x3w3 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-56fm-hfp3-x3w3 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-56fm-hfp3-x3w3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Impact wallabag was discovered to contain a Cross-Site Request Forgery (CSRF) which allows attackers to arbitrarily disable 2FA through `/config/otp/app/disable` and `/config/otp/email/disable`. This vulnerability has a CVSSv3.1 score of 4.3. **You should upgrade your instance to version 2.6.7 or higher.** ## Resolution These endpoints now require POST method. ## Credits We would like to thank @dhina016 for reporting this issue through huntr.dev. Reference: https://huntr.dev/bounties/4c446fe7-2a44-4907-b0cf-4ab77d75c487/
O3 Security · Impact-Aware SCA

Is GHSA-56fm-hfp3-x3w3 in your dependencies?

O3 Security finds GHSA-56fm-hfp3-x3w3 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-56fm-hfp3-x3w3: CSRF (Medium 4.3) | O3 Security