Skip to content

wallabag/wallabag Has Multiple Cross-Site Request Forgery (CSRF) Vulnerabilities

Moderate severity GitHub Reviewed Published Apr 8, 2025 in wallabag/wallabag • Updated Apr 9, 2025

Package

composer wallabag/wallabag (Composer)

Affected versions

< 2.6.11

Patched versions

2.6.11

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

References

@Kdecherf Kdecherf published to wallabag/wallabag Apr 8, 2025
Published to the GitHub Advisory Database Apr 9, 2025
Reviewed Apr 9, 2025
Last updated Apr 9, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

EPSS score

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-5pm7-cp8f-p2c2

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.