CVE-2025-67168: RiteCMS · n/a
Affects RiteCMSSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% 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:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubhandylulu/RiteCMSpkg:github/handylulu/RiteCMSOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2025-67168, European organizations should: 1) Upgrade RiteCMS to a version that implements secure password hashing algorithms such as bcrypt, Argon2, or PBKDF2 with appropriate salting and iteration counts. 2) If an upgrade is not immediately possible, implement compensating controls such as encrypting the database at rest with strong encryption and restricting access to the password storage backend. 3) Conduct a thorough audit of user accounts and enforce password resets to invalidate potentially compromised credentials. 4) Monitor access logs and network traffic for suspicious activity indicative of attempts to access or exfiltrate password data. 5) Employ multi-factor authentication (MFA) to reduce the impact of credential compromise. 6) Regularly back up data securely and test restoration procedures to minimize downtime in case of compromise. 7) Educate users and administrators about the risks associated with weak password storage and encourage strong password policies. 8) Implement network segmentation and least privilege principles to limit attacker movement if credentials are compromised.
Description
CVE-2025-67168 is a medium severity vulnerability in RiteCMS v3.1.0 where insecure encryption is used to store passwords. This flaw allows attackers to potentially recover user passwords if they gain access to the stored password data, impacting confidentiality but not integrity or availability. The vulnerability requires no authentication or user interaction and can be exploited remotely. While no known exploits are currently reported in the wild, the weakness in password storage practices poses a risk to user credential security. European organizations using RiteCMS v3.1.0 should prioritize remediation to prevent credential compromise. The vulnerability has a CVSS score of 5.