dbcve.org
DocmostApplication

CVE-2026-40927

MEDIUM · 5.4 CVSS v3.1 Published 2026-04-21
Fix available
A fix is available. Upgrade to 0.80.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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. Prior to 0.80.0, when leaving a comment on a page, it is possible to include a JavaScript URI as the link. When a user clicks on the link the JavaScript executes. This vulnerability is fixed in 0.80.0.

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 a stored Cross-Site Scripting (XSS) vulnerability in Docmost. An attacker can include a JavaScript URI (e.g., javascript:alert()) as a link within a comment on a page. When other users click this malicious link, the JavaScript code executes in their browser context, potentially allowing session hijacking or data theft.

MitigationUpgrade to Docmost version 0.80.0 or later, which includes proper input sanitization to neutralize JavaScript URIs in comment links.

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.80.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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 installed Docmost version
    Check the Docmost application version number in the software's about page, configuration file, or package metadata. This is typically visible in the admin dashboard under system information or can be found in the installed package version file.
    Affected if The installed version is less than 0.80.0
  2. Verify comments feature is in use
    Check whether the comments feature has been enabled and used on any workspace pages. Review the workspace or page settings where user-generated comments are posted.
    Affected if Comments are enabled and users have posted comments on any pages
  3. Inspect comment content for javascript: URIs
    Examine the stored comment data in the database or application logs for any links containing 'javascript:' URIs. Query the comments table or export comment content and search for the pattern 'javascript:' followed by any code.
    Affected if Any stored comment contains a link with a javascript: URI scheme
  4. Check recent user comment activity
    Review recent comments posted by users for any suspicious links, particularly those that execute JavaScript when clicked. Look for links starting with 'javascript:' in the comment display rendering.
    Affected if A comment with a javascript: link is rendered and clickable by other users

A user is affected if they are running Docmost version below 0.80.0 AND the application has comments enabled with user-submitted content that may contain javascript: URI links.

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.80.0 or later
Fixed in 0.80.0
Interim mitigation

Upgrade to Docmost version 0.80.0 or later, which includes proper input sanitization to neutralize JavaScript URIs in comment links.

Recommended fix High confidence

0.80.0

  1. 1. Backup your current Docmost instance and database before upgrading
  2. 2. Check the Docmost GitHub releases page (github.com) for version 0.80.0 and review the release notes
  3. 3. Upgrade Docmost to version 0.80.0 following the standard upgrade procedure for your deployment method
  4. 4. Verify the upgrade was successful by logging in and checking the version number
  5. 5. Test the comment functionality to ensure links are properly sanitized and JavaScript URIs are blocked

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
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40927 — 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-40927 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