CVE-2026-3795
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 doramart DoraCMS 3.0.x. Impacted is the function createFileBypath of the file /DoraCMS/server/app/router/api/v1.js. Performing a manipulation results in path traversal. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. 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 · high confidenceA path traversal vulnerability exists in DoraCMS 3.0.x within the createFileBypath function in the API router (/DoraCMS/server/app/router/api/v1.js). An attacker can manipulate the file path parameter to access or write files outside the intended directory, potentially achieving remote code execution or sensitive data exposure.
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 dataall versionsCVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Locate DoraCMS installation directorySearch for the DoraCMS directory structure, typically containing 'server/app/router/api/v1.js' path. Common locations include /opt/DoraCMS, /var/www/DoraCMS, or user home directories.Affected if DoraCMS is installed and the file /server/app/router/api/v1.js exists in the filesystem
-
Verify the vulnerable router file existsInspect the file at /server/app/router/api/v1.js within the DoraCMS installation and confirm it contains the createFileBypath function definition.Affected if The router file exists and exports the createFileBypath function handler
-
Check if the vulnerable endpoint is exposedReview server configuration (e.g., app.js, server.js, or route definitions) to determine if the API route using createFileBypath is registered and accessible via HTTP.Affected if The route is registered and the server is running with this API exposed
-
Test for lack of path traversal protectionExamine the createFileBypath function code in the router file to verify whether input validation exists for the file path parameter, specifically looking for '../' filtering or path.resolve() boundary checks.Affected if The function accepts a path parameter without validating or resolving it to a safe directory baseline
-
Identify if file creation permissions existCheck the filesystem permissions on directories where the function could write files, and verify if the Node.js process has write access to sensitive locations outside the intended upload directory.Affected if The application process has write permissions outside the designated upload directory and the function is reachable
A user is affected if DoraCMS is installed with the createFileBypath function exposed and accessible without proper path traversal validation on the file path parameter.
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 strict input validation on file path parameters to reject sequences like '../' and ensure files are created only within allowed directories using path.resolve() with boundary checking. Restrict or disable the createFileBypath function until properly secured.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3795 — 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-3795 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