Skip to main content
VulnerabilityPublished Updated

CVE-2023-51840: DoraCMS · Use of Hard-coded Credentials

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Jan 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
n/a n/aAffected
  • =2.1.8
Fixed in–

AI-suggested

Immediate mitigation steps include: 1) Conducting an inventory to identify all instances of DoraCMS 2.1.8 in use within the organization. 2) Restricting network access to CMS administrative interfaces using IP whitelisting or VPNs to limit exposure. 3) Implementing Web Application Firewalls (WAF) with custom rules to detect and block suspicious requests targeting cryptographic operations or authentication mechanisms. 4) Monitoring logs for unusual access patterns or failed authentication attempts that may indicate exploitation attempts. 5) If possible, replacing hard-coded keys by modifying the source code to use securely stored keys in environment variables or secure vaults, pending official patches. 6) Engaging with DoraCMS maintainers or community to obtain updates or patches as soon as they become available. 7) Educating development and security teams about the risks of hard-coded keys to prevent similar issues in future deployments.

Description

DoraCMS 2.1.8 is vulnerable to Use of Hard-coded Cryptographic Key.

References

Community reviews

Loading reviews…