Security Resilience

CVE-2023-0737

CSRF in Wallabag 2.5.2

Public PoCCSRF
Published
15 November 2024
Modified
19 November 2024
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
EPSS Score 0.0032 26th percentile
Risk Priority 49 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-0737 is a medium-severity CSRF (CWE-352) vulnerability in Wallabag. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Create Account (T1136); ranked at the 26th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-23 (Session Authenticity) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

wallabag version 2.5.2 contains a Cross-Site Request Forgery (CSRF) vulnerability that allows attackers to arbitrarily delete user accounts via the /account/delete endpoint. This issue is fixed in version 2.5.4.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1136 Create Account Persistence
Adversaries may create an account to maintain access to victim systems.
T1529 System Shutdown/Reboot Impact
Adversaries may shutdown/reboot systems to interrupt access to, or aid in the destruction of, those systems.
T1565 Data Manipulation Impact
Adversaries may insert, delete, or manipulate data in order to influence external outcomes or hide activity, thus threatening the integrity of the data.
T1586.001 Social Media Accounts Resource Development
Adversaries may compromise social media accounts that can be used during targeting.
T1098 Account Manipulation Persistence
Adversaries may manipulate accounts to maintain and/or elevate access to victim systems.
T1136.001 Local Account Persistence
Adversaries may create a local account to maintain access to victim systems.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-4455Same product: Wallabag Wallabag
CVE-2023-0735Same product: Wallabag Wallabag
CVE-2023-4454Same product: Wallabag Wallabag
CVE-2024-54414Shared CWE-352
CVE-2023-23705Shared CWE-352
CVE-2023-49821Shared CWE-352
CVE-2024-1976Shared CWE-352
CVE-2025-32673Shared CWE-352
CVE-2025-20321Shared CWE-352
CVE-2023-43275Shared CWE-352

Affected Assets

wallabag
wallabag
2.5.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.3.2
  • V3.5.1
  • V10.2.1

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Access enforcement requires verifying that state-changing requests originate from the authenticated user rather than a forged cross-site source.

Protecting session authenticity prevents attackers from replaying or forging authenticated requests via the victim's browser.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly require anti-CSRF controls such as tokens or SameSite attributes.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

A.8.29's combined programme of code review, SAST, and penetration testing reaches CSRF through both source and runtime channels: missing tokens and unprotected state-changing endpoints are standard SAST and pen-test findings. The remainder is bounded and nameable — subtle flaws in token validation logic, referer-checking bypasses, and CSRF in less common frameworks or non-HTML endpoints that automated tools flag inconsistently.

prevents

Training developers about CSRF and the need for tokens/SameSite cookies reduces instances where the weakness arises from ignorance, but CSRF is a specific implementation defect requiring correct technical countermeasures, and trained developers still introduce it through flawed token validation or missing protections — a minority effect, matching the A.6.3 -> CWE-598 anchor at the same rung.

prevents

A.8.28 mandates secure design, threat modelling, secure coding standards and SAST, which a well-implemented programme would extend to CSRF countermeasures (tokens, SameSite, Origin checks), but as a practice-mandating clause the actual coverage depends on implementation rigour, leaving a nameable remainder of instances where CSRF defences are not adopted.

prevents

A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CSRF is such a weakness, addressed when the supplier implements CSRF tokens and other protections under contracted secure coding/testing, but the effect is fallible and depends on the supplier's implementation, matching the A.8.30 -> CWE-134 anchor at the clause's declared ceiling of `partial`.

finds

A.8.8's reach is published advisories and component inventory; CSRF is overwhelmingly a first-party application design flaw, so A.8.8 only discovers it where it has already been published as a CVE in a third-party component (e.g., a web framework or CMS), which is a minority of latent CSRF instances — the same disclosure-bounded logic that graded A.8.8 -> CWE-89 at `partial`.

References