# CVE-2023-25264: Auth bypass in n/a

> Unauthenticated attackers can bypass authentication filters in Docmosis Tornado using crafted requests with relative path segments.

- **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:** 28 Feb 2023
- **Updated:** 18 Mar 2025
- **Also known as:** GHSA-xh63-f847-m5r7

## What is CVE-2023-25264?

CVE-2023-25264 is a high-severity authentication bypass vulnerability in n/a, published on 28 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Docmosis Tornado prior to version 2.9.5. An unauthenticated attacker can bypass the authentication check filter completely by introducing a specially crafted request with relative path segments.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2023-25264?

It affects 1 product.


Products: Docmosis Tornado.

## How do I fix CVE-2023-25264?

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

## Is CVE-2023-25264 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-42733](https://insights.sbomify.com/CVE-2024-42733/): Code injection in n/a (critical 9.8)
- [CVE-2023-25266](https://insights.sbomify.com/CVE-2023-25266/): Command injection in n/a (high 8.8)
- [CVE-2023-25265](https://insights.sbomify.com/CVE-2023-25265/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-25264 and fix it if it is affected.

What it is: CVE-2023-25264 is a high-severity authentication bypass vulnerability in n/a, published on 28 Feb 2023. 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-2023-25264 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-2023-25264/ (Markdown: https://insights.sbomify.com/CVE-2023-25264/index.md)
```

## Sources

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

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