# CVE-2025-2558: The Wound <= 0.0.1 - Unauthenticated LFI

> Unauthenticated attackers can exploit a path traversal vulnerability in the Wound WordPress theme to read arbitrary files from the server.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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:** 24 Apr 2025
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-4735-w7g7-ghx3

## What is CVE-2025-2558?

CVE-2025-2558 is a high-severity path traversal vulnerability in Unknown the-wound, published on 24 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The-wound WordPress theme through 0.0.1 does not validate some parameters before using them to generate paths passed to include function/s, allowing unauthenticated users to perform LFI attacks and download arbitrary file from the server

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

It affects 1 product.


Products: The Wound Project the Wound.

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

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

## Is CVE-2025-2558 being exploited?

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

Public exploit code:

- WordPress The Wound Theme <= 0.0.1 - Local File Inclusion (nuclei): http/cves/2025/CVE-2025-2558.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2558 is a high-severity path traversal vulnerability in Unknown the-wound, published on 24 Apr 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-2558 exists.

Affected product: Unknown the-wound. 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-2558/ (Markdown: https://insights.sbomify.com/CVE-2025-2558/index.md)
```

## Sources

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

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