CVE-2026-3794: Improper Authentication in doramart DoraCMS
A 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.
AI Analysis
Technical Summary
CVE-2026-3794 is a medium-severity improper authentication vulnerability discovered in doramart DoraCMS version 3.0.x, specifically within the Email API component at the endpoint /api/v1/mail/send. The vulnerability arises due to improper processing of requests to this API, which allows remote attackers to bypass authentication mechanisms entirely. The flaw requires no privileges, no user interaction, and can be exploited remotely over the network, making it relatively easy to leverage. The vulnerability affects the confidentiality, integrity, and availability of the affected system to a limited extent, as unauthorized actors could potentially send emails or perform other actions via the API, which may lead to information leakage or further attacks such as phishing or spam campaigns. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P) indicates no authentication or user interaction is required, with low attack complexity and partial impacts on confidentiality, integrity, and availability. The vendor has not issued any patches or advisories, and public exploit code is available, increasing the urgency for organizations to take mitigating actions. The vulnerability is currently not known to be exploited in the wild but poses a significant risk due to the availability of exploits and lack of vendor response.
Potential Impact
The improper authentication vulnerability in DoraCMS 3.0.x can allow remote attackers to bypass authentication controls on the Email API endpoint, potentially enabling unauthorized email sending or manipulation of email-related functions. This can lead to information disclosure, unauthorized actions within the CMS, and facilitate further attacks such as phishing, spam distribution, or lateral movement within the network. Organizations relying on DoraCMS for website or content management may face reputational damage, data breaches, or service disruption. The lack of vendor response and patches increases the risk of exploitation, especially since public exploit code is available. The impact is particularly concerning for organizations that use DoraCMS in customer-facing or critical communication roles, as attackers could abuse the email functionality to impersonate legitimate communications or exfiltrate data.
Mitigation Recommendations
Since no official patch or vendor response is available, organizations should implement the following mitigations: 1) Restrict network access to the vulnerable API endpoint (/api/v1/mail/send) using firewalls or web application firewalls (WAF) to allow only trusted IP addresses or internal networks. 2) Monitor and log all requests to the Email API endpoint for unusual or unauthorized activity. 3) Employ rate limiting and anomaly detection to detect and block suspicious email sending patterns. 4) If possible, disable or restrict the Email API functionality until a patch is available. 5) Conduct thorough security assessments and penetration tests to identify any exploitation attempts. 6) Keep DoraCMS installations isolated from critical internal systems to limit lateral movement. 7) Stay alert for any updates or patches from the vendor or community and apply them promptly. 8) Educate staff about phishing risks that could arise from exploitation of this vulnerability. These targeted controls go beyond generic advice by focusing on network-level restrictions, monitoring, and operational controls specific to the vulnerable API.
Affected Countries
China, United States, India, Germany, Brazil, Russia, South Korea, Japan, United Kingdom, France
CVE-2026-3794: Improper Authentication in doramart DoraCMS
Description
A 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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-3794 is a medium-severity improper authentication vulnerability discovered in doramart DoraCMS version 3.0.x, specifically within the Email API component at the endpoint /api/v1/mail/send. The vulnerability arises due to improper processing of requests to this API, which allows remote attackers to bypass authentication mechanisms entirely. The flaw requires no privileges, no user interaction, and can be exploited remotely over the network, making it relatively easy to leverage. The vulnerability affects the confidentiality, integrity, and availability of the affected system to a limited extent, as unauthorized actors could potentially send emails or perform other actions via the API, which may lead to information leakage or further attacks such as phishing or spam campaigns. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P) indicates no authentication or user interaction is required, with low attack complexity and partial impacts on confidentiality, integrity, and availability. The vendor has not issued any patches or advisories, and public exploit code is available, increasing the urgency for organizations to take mitigating actions. The vulnerability is currently not known to be exploited in the wild but poses a significant risk due to the availability of exploits and lack of vendor response.
Potential Impact
The improper authentication vulnerability in DoraCMS 3.0.x can allow remote attackers to bypass authentication controls on the Email API endpoint, potentially enabling unauthorized email sending or manipulation of email-related functions. This can lead to information disclosure, unauthorized actions within the CMS, and facilitate further attacks such as phishing, spam distribution, or lateral movement within the network. Organizations relying on DoraCMS for website or content management may face reputational damage, data breaches, or service disruption. The lack of vendor response and patches increases the risk of exploitation, especially since public exploit code is available. The impact is particularly concerning for organizations that use DoraCMS in customer-facing or critical communication roles, as attackers could abuse the email functionality to impersonate legitimate communications or exfiltrate data.
Mitigation Recommendations
Since no official patch or vendor response is available, organizations should implement the following mitigations: 1) Restrict network access to the vulnerable API endpoint (/api/v1/mail/send) using firewalls or web application firewalls (WAF) to allow only trusted IP addresses or internal networks. 2) Monitor and log all requests to the Email API endpoint for unusual or unauthorized activity. 3) Employ rate limiting and anomaly detection to detect and block suspicious email sending patterns. 4) If possible, disable or restrict the Email API functionality until a patch is available. 5) Conduct thorough security assessments and penetration tests to identify any exploitation attempts. 6) Keep DoraCMS installations isolated from critical internal systems to limit lateral movement. 7) Stay alert for any updates or patches from the vendor or community and apply them promptly. 8) Educate staff about phishing risks that could arise from exploitation of this vulnerability. These targeted controls go beyond generic advice by focusing on network-level restrictions, monitoring, and operational controls specific to the vulnerable API.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulDB
- Date Reserved
- 2026-03-08T07:31:54.271Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69ae2ef52904315ca3454d30
Added to database: 3/9/2026, 2:22:45 AM
Last enriched: 3/26/2026, 12:31:21 AM
Last updated: 4/28/2026, 7:04:14 AM
Views: 94
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.