# CVE-2025-67171: Path traversal in n/a

> Attackers can access sensitive files in RiteCMS via directory traversal due to incorrect access control in the templates component.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Dec 2025
- **Updated:** 17 Dec 2025
- **Also known as:** GHSA-59ww-88w5-m4g9

## What is CVE-2025-67171?

CVE-2025-67171 is a high-severity path traversal vulnerability in n/a, published on 17 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect access control in the /templates/ component of RiteCMS v3.1.0 allows attackers to access sensitive files via directory traversal.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-67171?

It affects 1 product.


Products: Ritecms Ritecms.

## How do I fix CVE-2025-67171?

No fix has been published for CVE-2025-67171 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-67171 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67171 exists.

## Other vulnerabilities in n/a

- [CVE-2020-23934](https://insights.sbomify.com/CVE-2020-23934/): File upload in n/a (high 8.8)
- [CVE-2025-67172](https://insights.sbomify.com/CVE-2025-67172/): Code injection in n/a (high 7.2)
- [CVE-2021-46367](https://insights.sbomify.com/CVE-2021-46367/): File upload in n/a (high 7.2)
- [CVE-2025-67173](https://insights.sbomify.com/CVE-2025-67173/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2013-5316](https://insights.sbomify.com/CVE-2013-5316/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-67171 and fix it if it is affected.

What it is: CVE-2025-67171 is a high-severity path traversal vulnerability in n/a, published on 17 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67171 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-67171/ (Markdown: https://insights.sbomify.com/CVE-2025-67171/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-67171
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-67171
- OSV: https://osv.dev/vulnerability/CVE-2025-67171

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-67171/
Summaries are generated and may contain mistakes; the official description above is the record.