Wallabag user can disable 2FA unintentionally
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 software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Composer package | wallabag/wallabag | >= 2.0.0-alpha.1, < 2.6.7 | 2.6.7 |
References
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N- Weakness (CWE)
-- Platform
- Composer
- Package
wallabag/wallabag- Disclosed
- 02.10.2023
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-56fm-hfp3-x3w3 - CC BY 4.0
Vulnerability history: wallabag/wallabag
All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 12
- First → latest
- 05.2022 04.2025
- Without a fix
- 1
- Exploited in attacks
- 0
Severity breakdown
- Medium 12
Disclosures per year
- 2022: 1
- 2023: 9
- 2024: 1
- 2025: 1
- 2026: 0
-
Wallabag user can disable 2FA unintentionally this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.