CVE-2025-10209
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA security flaw has been discovered in Papermerge DMS up to 3.5.3. This issue affects some unknown processing of the component Authorization Token Handler. Performing manipulation results in improper authorization. The attack can be initiated remotely. The exploit has been released to the public and may be exploited. The vendor was contacted early about this disclosure but did not respond in any way.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencePapermerge DMS versions up to 3.5.3 contain an improper authorization vulnerability in the Authorization Token Handler component. The vulnerability allows remote attackers to perform unauthorized actions by manipulating the authorization token handling logic. A public exploit is available, increasing the risk of active exploitation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Papermerge DMS versionQuery the running Papermerge instance via its API endpoint (e.g., /api/version) or inspect the container image tag, docker-compose file, or installation manifest that deployed the instanceAffected if The installed version is 3.5.3 or any earlier version (versions up to and including 3.5.3 are affected)
-
Confirm token-based authentication is in useVerify that the Papermerge DMS is configured to use token-based authentication for API or UI access. Check configuration files (papermerge.conf or settings.py) for AUTH_TOKEN settings or examine whether login produces a token responseAffected if Token-based authentication is enabled, as the vulnerability resides in the Authorization Token Handler component
-
Inspect access logs for anomalous token requestsReview Papermerge DMS access logs for unusual patterns such as repeated token validation failures, requests with manipulated token payloads, or unexpected authorization header patternsAffected if Logs show anomalous token-based requests or signs of token manipulation attempts
-
Check network exposure of DMS interfaceDetermine whether the Papermerge DMS web interface is publicly accessible or accessible from untrusted networks. Use network scanning or review firewall/load balancer rulesAffected if The DMS interface is exposed to the internet or untrusted networks, increasing exposure to remote attackers
-
Review for presence of public exploit indicatorsSearch for any indicators that the specific CVE-2025-10209 exploit has been used against the environment, such as unusual POST requests to token endpoints or unexpected privilege escalation patternsAffected if Evidence exists of exploit attempts or successful exploitation related to token handler manipulation
A Papermerge DMS installation is affected if it runs version 3.5.3 or earlier AND uses token-based authentication, regardless of whether the interface is publicly exposed (though public exposure increases risk due to the known public exploit).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper authorization checks in the token handler, validate token scopes and permissions on every request, and upgrade to a version beyond 3.5.3 once a patch is available. Until then, restrict network access to the DMS interface and monitor for anomalous token-based requests.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10209 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10209 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data