Warracker before 1.0.4 Missing Authorization via Paperless-ngx Document Linking
Warracker 1.0.0 to before 1.0.4 with Paperless-ngx integration enabled lets any non-admin user who owns a warranty read private Paperless-ngx documents the service account can read. Fixed in 1.0.4.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.0.4
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Paperless-ngx integration is enabled The configured Paperless-ngx API token can read the target document Attacker has a normal account that owns at least one warranty Affects Warracker versions before 1.0.4
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 14/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 1.0.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Warracker versions before 1.0.4 are affected, specifically its Paperless-ngx integration. An authenticated non-administrative user can link another user's private document to their own warranty and then read that document, exposing it without authorization.
Read the original description
Warracker before 1.0.4 contains a missing authorization vulnerability in its Paperless-ngx integration that allows an authenticated, non-administrative user to bypass document ownership restrictions by searching for and linking another user's private document ID to a warranty they own using the `other` document type. Attackers can exploit insufficient authorization checks in the `paperless_search_and_link()` and `serve_paperless_document()` route handlers in file_routes.py to retrieve and disclose private documents belonging to another user via the shared Paperless-ngx API credential, resulting in unauthorized read access and confidentiality loss.
What to do
Check whether your setup matches what the bug needs.
Paperless-ngx integration is enabled The configured Paperless-ngx API token can read the target document Attacker has a normal account that owns at least one warranty Affects Warracker versions before 1.0.4Upgrade to a fixed version: 1.0.4.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- sassanix Warracker
From 1.0.0 · fixed in 1.0.4
Evidence 3
- Advisory
- Patch
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120463
What does this mean?
Any signed-in non-administrative user who owns a warranty can read private Paperless-ngx documents that the Warracker service account can read, bypassing the owner-only restriction. This is a loss of confidentiality.Source: github.com, vulncheck.com
Am I affected, and how do I check?
Warracker versions 1.0.0 up to but not including 1.0.4 with the Paperless-ngx integration enabled. Check the installed Warracker version and whether the Paperless-ngx integration is turned on, and confirm that the configured API token can read the target document.Source: github.com, vulncheck.com
What should I do about it?
Upgrade Warracker to version 1.0.4 or later.Source: github.com, vulncheck.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data