CVE-2023-0610: wallabag subject to Improper Authorization via annotations

Published Feb 1, 2023
·
Updated

Impact 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.

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/

Other sources

Improper Authorization in GitHub repository wallabag/wallabag prior to 2.5.3.

wallabag subject to Improper Authorization via annotations

— Packagist

Affected Software

3 affected componentsFixes available
wallabag wallabag<2.5.3
composer/wallabag/wallabag>=2.0.0-beta.1, <2.5.3
2.5.3
composer/wallabag/wallabag>=2.0.0-beta.1<2.5.3
2.5.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/wallabag/wallabag to a version that resolves this vulnerability.

    Fixed in 2.5.3
  2. Upgrade

    Upgrade wallabag/wallabag to a version that resolves this vulnerability.

    Fixed in 2.5.3

Event History

Feb 1, 2023
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Feb 2, 2023
Advisory Published
via GitHub·07:26 PM
Data Sourced
via GitHub·07:26 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2023-0610?

The severity of CVE-2023-0610 is classified as a high-risk vulnerability due to improper authorization in Wallabag software.

2

How do I fix CVE-2023-0610?

To fix CVE-2023-0610, update Wallabag to version 2.5.3 or later.

3

What types of systems are affected by CVE-2023-0610?

CVE-2023-0610 affects all versions of Wallabag prior to 2.5.3.

4

What is the impact of CVE-2023-0610?

The impact of CVE-2023-0610 includes potential unauthorized access to sensitive user data.

5

Is there a workaround for CVE-2023-0610?

There is no known workaround for CVE-2023-0610; updating to the latest version is recommended.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203