GHSA-5pm7-cp8f-p2c2: wallabag/wallabag Has Multiple Cross-Site Request Forgery (CSRF) Vulnerabilities
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: wallabag/wallabag (Packagist) 2.6.11.
Low priority for now. Upgrade to wallabag/wallabag (Packagist) 2.6.11 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: OSV
## 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
- Published
- Apr 9, 2025
- Updated
- Apr 9, 2025
- EPSS
- —
- CWE
- CWE-352
Report tools
Action score
17
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| Packagist | wallabag/wallabag | pkg:composer/wallabag/wallabag |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Packagist | wallabag/wallabag | before 2.6.11 | 2.6.11 |
Same product
Packagist: all recordsOther highest-scoring records for the same primary product.
- GHSA-56fm-hfp3-x3w3Wallabag user can disable 2FA unintentionally17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Packagist:wallabag/wallabag | 2.6.11 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
- wallabag/wallabagcommit edffef8
- wallabag/wallabagcommit ed1acf5
- wallabag/wallabagcommit eb8408b
- wallabag/wallabagcommit e162408
- wallabag/wallabagcommit ddf2e80
- wallabag/wallabagcommit d703fa6
- wallabag/wallabagcommit d1e1289
- wallabag/wallabagcommit cf49be6
- wallabag/wallabagcommit ac5b5fb
- wallabag/wallabagcommit 99c8a06
- wallabag/wallabagcommit 6fa61c0
- wallabag/wallabagcommit 677b298
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-352 · Cross-Site Request Forgery (CSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
osv
Root cause
State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.
The bug in code
The whole CWE-352 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use(session({ cookie: { httpOnly: true } }));
app.post("/account/address", updateAddress);Fixed
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));
app.post("/account/address", csrfProtection, updateAddress);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- github.com/wallabag/wallabag/commit/edffef837598355c9bec433c469f1e04c35b27cb
- github.com/wallabag/wallabag/commit/ed1acf59e166a2a6bb81c52baaeabd6196feae98
- github.com/wallabag/wallabag/commit/eb8408b22fbaa6b3d78047d6203b23b7f52bbf03
- github.com/wallabag/wallabag/commit/e162408139ac9bb12e69f4d49de45ade49369c21
- github.com/wallabag/wallabag/commit/ddf2e808422e41ea55cebf2aa12eb1823c5c340a
- github.com/wallabag/wallabag/commit/d703fa6a3a75f7c3b433e8caf618bfb0a9a0ba63
- github.com/wallabag/wallabag/commit/d1e128900acc0cb8c88eb7a085c9ef5420cf0c43
- github.com/wallabag/wallabag/commit/cf49be694089667bbab9f10d52862fbdba9a89de
- github.com/wallabag/wallabag/commit/ac5b5fb379233d6e96ea14ae21b7f88761d5fa3f
- github.com/wallabag/wallabag/commit/99c8a06594d6ee7480ce4d041ccff3025b353656
- github.com/wallabag/wallabag/commit/6fa61c0f9c48d37625c92a8913b487230761fb47
- github.com/wallabag/wallabag/commit/677b2986bc78df4c7ecfed87a24593fa0553fd3c
- github.com/wallabag/wallabag/commit/5ea5115a721651f2af349e8451be8947dad9c814
- github.com/wallabag/wallabag/commit/3817010e29ed368df271cdd11ec71a46a341c673
- github.com/wallabag/wallabag/commit/27f0d94db72fb2a54b5965e4e9908a0f418f44b5
- github.com/wallabag/wallabag/commit/264f91126e2c42188b80848c881264da743b4dc1
- github.com/wallabag/wallabag/commit/0d8429dfc77b84f50060b253fd84f1c09b892226
- github.com/wallabag/wallabag/commit/00d0e6f951927434039465b4d3ae3dd661911172
- github.com/wallabag/wallabag
Vendor advisories and official records. Exploit/PoC links are deliberately left out.