Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify exposed RiteCMS /templates/ endpoint
-
DeliveryCraft request with traversal sequences
-
ExploitEscape intended directory via path traversal
-
ExecutionRead sensitive server files
-
ImpactHarvest disclosed credentials/config
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires a network-reachable RiteCMS 3.1.0 instance with the /templates/ component accessible; the attacker supplies directory-traversal sequences to that component to read files outside the intended path. Per CVSS PR:N/UI:N, no authentication or user interaction is indicated, and the single affected version (3.1.0) limits exposure to that specific release. Impact is confined to confidentiality (reading sensitive files) - there is no integrity or availability effect - so the practical limit is the small population of deployed RiteCMS 3.1.0 instances rather than any special configuration requirement. |
| Impact | Signals are moderately consistent but point to a lower real-world priority than the 7.5 CVSS 'High' score alone suggests. The CVSS vector (AV:N/AC:L/PR:N/UI:N) describes a remotely reachable, low-complexity, unauthenticated flaw with high confidentiality impact only (C:H/I:N/A:N), which aligns well with a CWE-22 directory traversal exposing sensitive files. Public exploit code exists (POC via a GitHub research repo), which raises practical exploitability. However, the vulnerability is NOT listed in CISA KEV, and no EPSS score was provided in the input, so there is no evidence of active or widespread exploitation - the POC indicates capability, not confirmed abuse. The dominant mitigating factor is the target: RiteCMS is a niche flat-file CMS with a very small deployment footprint, so even a trivially exploitable unauthenticated read is unlikely to be mass-exploited. Net: a genuine, easily weaponizable information-disclosure bug, but realistically a low-to-moderate priority outside environments known to run RiteCMS 3.1.0. Note the description frames the issue as 'incorrect access control' combined with traversal - verify with the vendor/POC whether any authentication is actually required, as that would change the PR metric. |
| Exploit ScenarioDerived | An unauthenticated remote attacker sends a crafted request to the RiteCMS /templates/ component using directory-traversal sequences (e.g. ../../) to escape the intended directory and read arbitrary sensitive files such as configuration or credential files. Public exploit code for CVE-2025-67171 is available on GitHub, lowering the skill required. Because the CVSS vector is AV:N/AC:L/PR:N, the request can be issued directly over the network against a reachable instance without user interaction. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Directory traversal in RiteCMS 3.1.0's /templates/ component allows unauthenticated remote attackers to read files outside the intended templates path, affecting confidentiality only. The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N confirms network exploitable, low complexity, no authentication or user interaction, high confidentiality impact, and no integrity/availability impact; publicly available exploit code exists, but no CISA KEV active-exploitation signal is present. Exploitation requires a network-reachable RiteCMS 3.1.0 instance with the /templates/ component accessible, and the single affected version limits real-world exposure.
RemediationAI
No vendor-released patch identified at time of analysis. Until an official fix is available, restrict external access to the /templates/ component at the reverse proxy or web server (for example, deny direct requests to /templates/ unless explicitly required), which reduces exposure but may break legitimate template-serving functionality if that path is used by the application; test in staging before enforcement. Apply strict input validation and canonicalization for any file or template path parameter, reject or normalize ../ and encoded traversal sequences, and run the CMS process with least privilege so a successful traversal cannot read unrelated OS or configuration files; these controls reduce impact but do not eliminate the underlying flaw. Monitor https://github.com/handylulu/RiteCMS/ for a fixed release and watch the exploit reference https://github.com/mbiesiad/vulnerability-research/tree/main/CVE-2025-67171 for updated indicators; WAF traversal rules can help but may be bypassed with alternate encodings, so do not rely on them as the sole control.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
RiteCMS is a PHP-based content management system; CVE-2025-67171 is a CWE-22 path traversal in the /templates/ component of version 3.1.0. The component appears to accept a file or template path and resolve it against the filesystem without sufficient canonicalization or confinement to the intended templates directory, allowing ../ sequences to escape and disclose sensitive files. The affected CPE cpe:2.3:a:ritecms:ritecms:3.1.0:*:*:*:*:*:*:* confirms that only 3.1.0 is in scope. The supplied CVSS vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N maps to a remote, low-complexity, unauthenticated read primitive with no user interaction and no scope change; because the impact is confidentiality-only, the practical risk is bounded by the population of exposed RiteCMS 3.1.0 installations. A public proof-of-concept is linked in the mbiesiad/vulnerability-research repository.
Know when Ritecms gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Remote, low-complexity path traversal with no auth or interaction indicated; impact is sensitive-file disclosure only, so C:H with I:N/A:N.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
DescriptionCVE.org
Incorrect access control in the /templates/ component of RiteCMS v3.1.0 allows attackers to access sensitive files via directory traversal.
Executive ViewAI
RiteCMS 3.1.0 contains a high-severity unauthenticated file-read flaw affecting its /templates/ component, allowing attackers to access files outside the intended templates path and potentially exposing sensitive data. Publicly available exploit code exists; No vendor-released patch identified at time of analysis, so any internet-facing RiteCMS 3.1.0 instance represents a data-confidentiality risk. Leadership should prioritize identifying affected deployments because the issue can be exploited without credentials or user interaction.
No vendor-released patch identified at time of analysis; restrict access to the RiteCMS 3.1.0 /templates/ endpoint via network controls or WAF, block directory traversal sequences, run with least privilege, monitor file access, and plan migration or decommission.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
Affected Products (CPE)CVE.org
An issue was discovered in RiteCMS 2.2.1. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, lo
Authenticated remote code execution in RiteCMS 3.1.0 allows an attacker holding a high-privileged administrative session
Cross-site request forgery (CSRF) vulnerability in RiteCMS 1.0.0 allows remote attackers to hijack the authentication of
RiteCMS version 3.1.0 and below suffers from an arbitrary file deletion via path traversal vulnerability in Admin Panel.
RiteCMS version 3.1.0 and below suffers from an arbitrary file overwrite via path traversal vulnerability in Admin Panel
RiteCMS v3.0.0 was discovered to contain a cross-site scripting (XSS) vulnerability via the component main_menu/edit_sec
Rite CMS 3.0 has Multiple Cross-Site scripting (XSS) vulnerabilities that allow attackers to execute arbitrary code via
Weak password storage in RiteCMS v3.1.0 (CWE-916) allows anyone who obtains the stored credential values to recover user
A File upload vulnerability in RiteCMS 3.0 allows a local attacker to upload a SVG file with XSS content. Rated medium s
Rite CMS 3.0 has Multiple Cross-Site scripting (XSS) vulnerabilities that allow attackers to execute arbitrary code via
Rite CMS 3.0 has a Cross-Site scripting (XSS) vulnerability that allows attackers to execute arbitrary code via a crafte
Cross-site scripting (XSS) vulnerability in RiteCMS 1.0.0 allows remote authenticated users to inject arbitrary web scri
NVD
CVE.org
EPSS
GitHub
Exploit-DB