CVE-2026-30235
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 · uneditedOpenProject is an open-source, web-based project management software. Prior to 17.2.0, this vulnerability occurs due to improper validation of OpenProject’s Markdown rendering, specifically in the hyperlink handling. This allows an attacker to inject malicious hyperlink payloads that perform DOM clobbering. DOM clobbering can crash or blank the entire page by overwriting native DOM functions with HTML elements, causing critical JavaScript calls to throw runtime errors during application initialization and halt further execution. This vulnerability is fixed in 17.2.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 confidenceOpenProject before 17.2.0 has improper validation in its Markdown rendering engine's hyperlink handling, allowing attackers to inject malicious hyperlink payloads that perform DOM clobbering. This overwrites native DOM functions with HTML elements, causing critical JavaScript calls to throw runtime errors during application initialization and potentially blank or crash the page.
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< 17.2.0CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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.
-
Identify installed OpenProject versionCheck the OpenProject administration interface (Admin > Information) or look for a version file in the installation directory. If using Docker, run: docker exec <container> cat /app/Gemfile.lock | grep openproject or check the UI footer for version number.Affected if The displayed version is below 17.2.0 (for example, 17.1.0, 17.0.0, 12.x, etc.)
-
Confirm Markdown feature is in useOpenProject uses Markdown for project descriptions, work package descriptions, wiki pages, and news entries. Check if any of these features contain user-submitted or imported hyperlink content.Affected if Markdown rendering is enabled and the instance processes user-supplied hyperlinks in descriptions, comments, or imported content.
-
Check browser console for DOM-related errorsOpen the browser developer console (F12) while loading OpenProject pages. Look for JavaScript errors mentioning 'not a function', 'is not a function', or TypeError messages that suggest DOM element references are being called as functions.Affected if JavaScript errors appear in the console referencing native DOM methods behaving unexpectedly, which may indicate DOM clobbering has occurred.
-
Inspect rendered HTML for suspicious hyperlink attributesView page source or use browser developer tools to inspect hyperlinks in rendered Markdown content. Look for anchor tags where href attributes contain unusual attribute injection patterns (such as multiple id attributes or overridden element references).Affected if Rendered hyperlinks contain unexpected attributes or the DOM structure shows elements with overlapping IDs that could overwrite native properties.
You are affected if your OpenProject version is below 17.2.0 AND your instance processes Markdown content with hyperlinks (which is the default configuration).
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.
dbcve · scoped17.2.0
Upgrade OpenProject to version 17.2.0 or later to receive the patch for the Markdown hyperlink validation fix.
17.2.0
- Backup your OpenProject database and configuration files before upgrading
- Check your current OpenProject version to confirm it is below 17.2.0
- Upgrade OpenProject to version 17.2.0 or later using your package manager or upgrade procedure
- Verify the upgrade was successful by checking the OpenProject version and testing Markdown rendering functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-30235 — 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-2026-30235 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