CVE-2023-0609: wallabag contains Improper Authorization via export feature

Published Feb 1, 2023
·
Updated

Description

The export feature lets a user export a single entry or a set of entries in a given format (e.g. PDF, MOBI, TXT).

For example, https://yourinstance.wallabag.org/export/45.pdf will export the entry with id 45 in PDF format.

Since wallabag 2.0.0-alpha.1, this feature is vulnerable to an insecure direct object reference attack. A logged user can export any single entry without ownership validation.

This is due to a lack of access validation in the downloadEntryAction method.

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 method before sending the exported entry.

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

Workaround

If you are unable to update to the latest version or if you want to temporarily limit risk of exploitation, you may consider blocking requests to the endpoint /export/.

E.g. with nginx:

nginx location /export { deny all; }

Credits

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

Reference: https://www.huntr.dev/bounties/3adef66f-fc86-4e6d-a540-2ffa59342ff0/

Other sources

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

wallabag contains Improper Authorization via export feature

— Packagist

Affected Software

3 affected componentsFixes available
wallabag wallabag<2.5.3
composer/wallabag/wallabag>=2.0.0-alpha.1, <2.5.3
2.5.3
composer/wallabag/wallabag>=2.0.0-alpha.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
  3. Compensating control

    Temporarily block requests to the /export/* endpoint; with nginx, deny access to the /export location using 'deny all;'.

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
DescriptionSeverityWeaknessAffected Software
Data Sourced
via Packagist·07:26 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2023-0609?

CVE-2023-0609 has been categorized as a medium severity vulnerability.

2

How do I fix CVE-2023-0609?

To remediate CVE-2023-0609, users should upgrade to Wallabag version 2.5.3 or higher.

3

What type of vulnerability is CVE-2023-0609?

CVE-2023-0609 is an improper authorization vulnerability.

4

Is my version affected by CVE-2023-0609?

All versions of Wallabag prior to 2.5.3 are affected by CVE-2023-0609.

5

What impact does CVE-2023-0609 have?

CVE-2023-0609 allows unauthorized access to sensitive information in the affected software.

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