dbcve.org
DocmostApplication

CVE-2026-34213

MEDIUM · 5.4 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 0.71.0 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Docmost is open-source collaborative wiki and documentation software. Starting in version 0.3.0 and prior to version 0.71.0, improper authorization in Docmost allows a low-privileged authenticated user to overwrite another page's attachment within the same workspace by supplying a victim `attachmentId` to `POST /api/files/upload`. This is a remote integrity issue requiring no victim interaction. Version 0.71.0 contains a patch.

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 · high confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability where the file upload endpoint (`POST /api/files/upload`) lacks proper authorization checks. A low-privileged authenticated user can overwrite attachments belonging to other pages within the same workspace by specifying a victim `attachmentId`, achieving unauthorized file modification without any victim interaction.

MitigationUpgrade Docmost to version 0.71.0 or later to obtain the patch. If immediate upgrading is not feasible, implement proper ownership verification on the file upload endpoint to ensure users can only upload to attachments they own or have explicit permission to modify.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DocmostApplication
Affected:>= 0.3.0, < 0.71.0

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Docmost installation version
    Check the running Docker image tag, package.json version field, or query the Docmost API health endpoint for version information
    Affected if The installed version is 0.3.0 or higher but below 0.71.0
  2. Confirm user authentication is enabled
    Verify that Docmost user authentication is configured and functional by attempting to log in with a test account or reviewing authentication settings in the configuration
    Affected if User authentication is required for this vulnerability, so unauthenticated instances are not affected
  3. Check for low-privilege user accounts
    Review user roles and permissions in Docmost admin panel or database to identify non-owner users with limited workspace privileges
    Affected if Low-privilege users exist within any workspace who could potentially manipulate the attachmentId parameter
  4. Verify file upload API is accessible
    Confirm the POST /api/files/upload endpoint is reachable by reviewing API routing configuration or testing with a valid authentication token
    Affected if The file upload endpoint is exposed and accepts requests with an attachmentId parameter in the request body

You are affected if Docmost version is 0.3.0 or higher but below 0.71.0, user authentication is enabled, and low-privilege users can access the file upload API endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 0.71.0 or later
Fixed in 0.71.0
Interim mitigation

Upgrade Docmost to version 0.71.0 or later to obtain the patch. If immediate upgrading is not feasible, implement proper ownership verification on the file upload endpoint to ensure users can only upload to attachments they own or have explicit permission to modify.

Recommended fix High confidence

0.71.0

  1. Back up the current Docmost installation and database before upgrading
  2. Stop the running Docmost service
  3. Download Docmost version 0.71.0 from the official repository
  4. Replace the existing Docmost application files with the new version 0.71.0
  5. Run any pending database migrations if applicable (check for migration scripts in the upgrade)
  6. Start the Docmost service
  7. Verify that the application is running correctly and the /api/files/upload endpoint now properly validates authorization
  8. Test that low-privileged users can no longer overwrite attachments belonging to other pages

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Docmost Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34213 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34213 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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