dbcve.org
DoracmsApplication · Html Js

CVE-2024-28715

HIGH · 8.8 CVSS v3.1 Published 2024-03-19
Fix available
A fix is available. Upgrade to after 2.18 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross Site Scripting vulnerability in DOraCMS v.2.18 and before allows a remote attacker to execute arbitrary code via the markdown0 function in the /app/public/apidoc/oas3/wrap-components/markdown.jsx endpoint.

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

Cross Site Scripting vulnerability in DOraCMS v2.18 and prior allows remote attackers to inject malicious JavaScript through the markdown0 function at /app/public/apidoc/oas3/wrap-components/markdown.jsx, enabling arbitrary code execution in victim browsers.

MitigationImplement strict input validation and output encoding on the markdown parsing component; upgrade to a patched version if available.

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
DoracmsApplication
Affected:<= 2.18

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

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

  1. Verify DOraCMS installation
    Locate the DOraCMS application installation directory and check for package.json file, or identify running processes hosting DOraCMS
    Affected if DOraCMS is not installed or the application is not present in the environment
  2. Check installed version
    Examine the package.json file in the DOraCMS root directory for the 'version' field, or query the installed package via npm list doracms or equivalent package manager command
    Affected if The installed version is 2.18 or lower (any version <= 2.18)
  3. Verify vulnerable component exists
    Check if the file /app/public/apidoc/oas3/wrap-components/markdown.jsx exists within the DOraCMS installation directory
    Affected if The file markdown.jsx exists in the path /app/public/apidoc/oas3/wrap-components/
  4. Confirm API documentation endpoint is accessible
    Test access to the /apidoc/oas3 endpoint (or /app/public/apidoc/oas3/) on the DOraCMS server using a web browser or curl command
    Affected if The OAS3 API documentation endpoint is publicly or internally accessible without authentication

The environment is affected if DOraCMS version 2.18 or lower is installed, the vulnerable markdown.jsx file exists, and the /apidoc/oas3 endpoint is accessible.

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.

From vendor data
Upgrade available Upgrade to a release after 2.18
Interim mitigation

Implement strict input validation and output encoding on the markdown parsing component; upgrade to a patched version if available.

Fix this in Doracms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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