VulnerabilityPublished 17 Dec 2025

CVE-2025-67171: RiteCMS · CVE-2025-67171 is a high-severity

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.8% chance of exploitation in 30 days – higher than 56% 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:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2025-67171, organizations should first verify if they are running RiteCMS version 3.1.0 and restrict public access to the /templates/ directory until a patch or update is available. Implement strict input validation and sanitization on all file path parameters to prevent directory traversal sequences such as '../'. Employ web application firewalls (WAFs) with custom rules to detect and block traversal attempts targeting the /templates/ component. Conduct thorough code reviews and security testing focusing on access control mechanisms within the CMS, especially for file handling functions. Monitor server logs for unusual access patterns or attempts to access sensitive files outside the intended directories. If possible, isolate the CMS environment and limit file permissions to minimize the exposure of sensitive files. Engage with the RiteCMS vendor or community to obtain patches or security advisories and apply updates promptly once released. Additionally, educate development and operations teams about secure coding practices related to file access controls.

Description

CVE-2025-67171 is a high-severity vulnerability in RiteCMS v3.1.0 caused by incorrect access control in the /templates/ component, enabling unauthenticated attackers to perform directory traversal and access sensitive files. The vulnerability has a CVSS score of 7.5, indicating a significant confidentiality impact without affecting integrity or availability. Exploitation requires no privileges or user interaction and can be performed remotely over the network. Although no known exploits are currently reported in the wild, the flaw allows attackers to read sensitive data, potentially leading to information disclosure. European organizations using RiteCMS should prioritize patching or applying mitigations to prevent unauthorized file access. Countries with higher adoption of RiteCMS or with strategic targets using this CMS are at greater risk. Mitigation involves restricting directory traversal vectors, implementing strict input validation, and monitoring access to sensitive directories.

Impact

For European organizations, the impact of CVE-2025-67171 centers on unauthorized disclosure of sensitive information hosted on RiteCMS-powered websites or intranet portals. This can lead to exposure of confidential business data, user credentials, or internal configuration details, potentially facilitating subsequent attacks such as privilege escalation, phishing, or lateral movement within networks. Organizations in sectors like government, finance, healthcare, and critical infrastructure that rely on RiteCMS for content management may face increased risk of data breaches and regulatory non-compliance under GDPR. The confidentiality breach could damage organizational reputation and result in financial penalties. Since the vulnerability does not affect data integrity or availability, direct service disruption is unlikely, but the information disclosure alone poses a significant threat. The ease of exploitation without authentication means attackers can operate stealthily and at scale, increasing the likelihood of widespread impact if the vulnerability is not addressed promptly.

Summary

CVE-2025-67171 is a directory traversal vulnerability identified in the /templates/ component of RiteCMS version 3.1.0. The root cause is incorrect access control that fails to properly sanitize or restrict file path inputs, allowing attackers to traverse directories beyond the intended scope. This enables unauthorized access to sensitive files on the server, which may include configuration files, source code, or other confidential data. The vulnerability is exploitable remotely over the network without requiring any authentication or user interaction, increasing its risk profile. The CVSS 3.1 base score of 7.5 reflects a high severity primarily due to the confidentiality impact, as attackers can read sensitive information but cannot modify data or disrupt service availability. The CWE-22 classification confirms the issue as a path traversal flaw. No patches or known exploits are currently documented, but the vulnerability's presence in a CMS component commonly exposed to the internet makes it a critical concern. Attackers could leverage this flaw to gather intelligence for further attacks or to compromise user privacy. The lack of authentication requirements and ease of exploitation highlight the need for immediate mitigation efforts.

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 24 Dec 2025, 19:33 UTC

WeaknessesCWE-22

Technical details

References

Community reviews

Related threats