GHSA-gjvc-55fw-v6vq is a medium-severity (CVSS 6.5) Cross-Site Request Forgery (CSRF) vulnerability in wallabag/wallabag. 1 public exploit reference exists, so weaponization risk is real. A fix is available for wallabag/wallabag — see the affected versions and patch details below.
Wallabag user can delete own API client unintentionally
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-gjvc-55fw-v6vq.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-gjvc-55fw-v6vq plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
wallabag/wallabagReal-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
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/
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | wallabag/wallabag | ≥ 2.0.0-alpha.1&&< 2.6.3 | 2.6.3composer require wallabag/wallabag:^2.6.3 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
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.
Fix
Update wallabag/wallabag to 2.6.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gjvc-55fw-v6vq is resolved across your whole dependency graph.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-gjvc-55fw-v6vq can be triaged on real exposure rather than presence alone.
Tailored to GHSA-gjvc-55fw-v6vq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-gjvc-55fw-v6vq in your dependencies?
O3 Security finds GHSA-gjvc-55fw-v6vq across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.