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

> A remote attacker can achieve Remote Code Execution in Swetrix Web Analytics API via a crafted HTTP request exploiting a directory traversal vulnerability.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2025
- **Updated:** 26 Sep 2025
- **Also known as:** GHSA-6q94-xgm6-vjmf

## What is CVE-2025-59304?

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

### Official description

A directory traversal issue in Swetrix Web Analytics API 3.1.1 before 7d8b972 allows a remote attacker to achieve Remote Code Execution via a crafted HTTP request.

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

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

It affects 1 product.


Products: Swetrix Swetrix.

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

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

## Is CVE-2025-59304 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59304 is a critical path traversal vulnerability in n/a, published on 17 Sep 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-59304 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-59304/ (Markdown: https://insights.sbomify.com/CVE-2025-59304/index.md)
```

## Sources

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

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