CVE-2025-67168
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-17

Last updated on: 2025-12-18

Assigner: MITRE

Description
RiteCMS v3.1.0 was discovered to use insecure encryption to store passwords.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-17
Last Modified
2025-12-18
Generated
2026-06-16
AI Q&A
2025-12-17
EPSS Evaluated
2026-06-14
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
ritecms ritecms 3.1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-916 The product generates a hash for a password, but it uses a scheme that does not provide a sufficient level of computational effort that would make password cracking attacks infeasible or expensive.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

RiteCMS version 3.1.0 uses insecure encryption methods to store user passwords, which means the passwords are not adequately protected and could be more easily accessed or compromised by attackers.

Impact Analysis

This vulnerability can lead to unauthorized access to user accounts if attackers are able to exploit the weak password encryption. It increases the risk of password theft and potential account compromise.

Detection Guidance

You can detect this vulnerability by checking if your system is running RiteCMS version 3.1.0, which uses insecure encryption for storing passwords. To identify this, you can look for the presence of RiteCMS files, especially the functions.admin.inc.php file in the cms/includes directory. Commands such as 'grep -r "RiteCMS v3.1.0" /path/to/webroot' or 'find /path/to/webroot -name functions.admin.inc.php' can help locate relevant files. Additionally, reviewing the encryption methods used in the password storage code can confirm the vulnerability. [1, 2]

Mitigation Strategies

Immediate mitigation steps include upgrading RiteCMS to a version that uses secure password encryption if available. If no update is available, you should consider manually modifying the password storage mechanism to use a secure hashing algorithm. Additionally, enforce password resets for all users to ensure compromised passwords are changed. Restrict network access to the CMS administration interface and monitor for suspicious activity. [1, 2]

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-67168. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart