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

> An arbitrary file read vulnerability in PerfreeBlog allows attackers to access sensitive files via the getThemeFileContent function.

- **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:** 25 Aug 2025
- **Updated:** 26 Aug 2025
- **Also known as:** GHSA-9hhq-2xjw-3mqv

## What is CVE-2025-29421?

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

### Official description

PerfreeBlog v4.0.11 has an arbitrary file read vulnerability in the getThemeFileContent function.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Perfree Perfreeblog.

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

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

## Is CVE-2025-29421 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-30333](https://insights.sbomify.com/CVE-2023-30333/): File upload in n/a (critical 9.8)
- [CVE-2023-27757](https://insights.sbomify.com/CVE-2023-27757/): File upload in n/a (critical 9.8)
- [CVE-2025-29281](https://insights.sbomify.com/CVE-2025-29281/): File upload in n/a (high 8.8)
- [CVE-2025-60730](https://insights.sbomify.com/CVE-2025-60730/): Path traversal in n/a (high 7.6)
- [CVE-2025-60731](https://insights.sbomify.com/CVE-2025-60731/): File upload in n/a (high 7.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-29421 is a high-severity path traversal vulnerability in n/a, published on 25 Aug 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-29421 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-29421/ (Markdown: https://insights.sbomify.com/CVE-2025-29421/index.md)
```

## Sources

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

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