Skip to main content
VulnerabilityPublished

CVE-2026-53692: Redeight CMS · Use of Weak Hash

Affects Redeight CMSSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 4.0 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 13 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
RedeightRedeight CMSAffected
  • =1.0
Fixed in–

AI-suggested

Until a fix is available, it is recommended to avoid using Redeight CMS version 1.0 in sensitive environments or implement compensating controls such as restricting access to password hash storage. Consider upgrading to a version that uses a secure password hashing algorithm with salting once available.

Description

Redeight CMS version 1.0 uses the MD5 algorithm without a salt to store user passwords. Because MD5 is a cryptographically broken algorithm and lacks salting, attackers who obtain the password hashes can trivially reverse them using rainbow tables, leading to the exposure of plaintext credentials.

References

Community reviews

Loading reviews…