CVE-2026-3794
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 vulnerability was identified in doramart DoraCMS 3.0.x. This issue affects some unknown processing of the file /api/v1/mail/send of the component Email API. Such manipulation leads to improper authentication. It is possible to launch the attack remotely. The exploit is publicly available and might be used. 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 · moderate confidenceThe vulnerability is an authentication bypass in the DoraCMS 3.0.x mail API endpoint (/api/v1/mail/send). The email API component fails to properly authenticate requests, allowing remote attackers to send emails without authorization. A publicly available exploit increases the likelihood of active targeting.
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.
-
Confirm DoraCMS installationLocate the DoraCMS application by checking for package.json with doracms dependency, or the presence of app directory structure (views, routes, controllers folders) in the web rootAffected if DoraCMS or Html Js Doracms is present on the system
-
Verify mail API route existsExamine the routes configuration files (typically in /routes or the main app.js) for the /api/v1/mail/send endpoint definitionAffected if The /api/v1/mail/send route is defined in the application routes
-
Check route authentication middlewareInspect the route handler for /api/v1/mail/send to determine if any authentication middleware (such as passport, session checks, or token validation) is applied before the mail sending logicAffected if No authentication middleware is attached to the mail send route, or the middleware is conditionally bypassed
-
Test endpoint without credentialsSend a curl or similar HTTP request to the /api/v1/mail/send endpoint with no authorization headers, cookies, or tokensAffected if The endpoint accepts and processes the request without returning an authentication error (401/403)
-
Review API route registration orderCheck the main routes file to see how the mail endpoint is registered relative to any global authentication middleware - specific routes registered before global middleware may bypass authAffected if The mail send route is registered before or outside the global auth middleware chain
If DoraCMS is present and the /api/v1/mail/send endpoint processes requests without requiring valid authentication credentials, the environment is affected by this CVE.
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 proper authentication and authorization checks on the /api/v1/mail/send endpoint to ensure only authenticated and authorized users can send emails. Consider adding rate limiting and input validation as defense-in-depth measures.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3794 — 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-3794 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