CVE-2023-0610

wallabag subject to Improper Authorization via annotations

Resolution

A user check is now done in the vulnerable methods before applying change on an annotation.

The Annotation retrieval through a ParamConverter has also been replaced with a call to the AnnotationRepository in order to prevent any information disclosure through response discrepancy.

Workarounds

Credits

We would like to thank @bAuh0lz for reporting this issue through huntr.dev.

Reference: https://huntr.dev/bounties/8fdd9b31-d89b-4bbe-9557-20b960faf926/

The annotations feature lets users add annotations on highlighted parts of an entry.

The controller does not validate authorization on PUT and DELETE requests which lets a logged user modify or delete any annotation using their ID on their endpoints example.org/annotations/{id}.

These vulnerable requests also disclose highlighted parts of the entry to the attacker.

You should immediately patch your instance to version 2.5.3 or higher if you have more than one user and/or having open registration.

CVE-2023-0610 has a CVSS score of 5.4 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.5.3); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2023-0610? CVE-2023-0610 is a medium-severity security vulnerability in wallabag/wallabag (composer), affecting versions >= 2.0.0-beta.1, < 2.5.3. It is fixed in 2.5.3.
2. How severe is CVE-2023-0610? CVE-2023-0610 has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of wallabag/wallabag are affected by CVE-2023-0610? wallabag/wallabag (composer) versions >= 2.0.0-beta.1, < 2.5.3 is affected.
4. Is there a fix for CVE-2023-0610? Yes. CVE-2023-0610 is fixed in 2.5.3. Upgrade to this version or later.
5. Is CVE-2023-0610 exploitable, and should I be worried? Whether CVE-2023-0610 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2023-0610 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2023-0610? Upgrade wallabag/wallabag to 2.5.3 or later.

Other vulnerabilities in wallabag/wallabag