# CVE-2025-1743: zyx0814 Pichome index.php path traversal

> Remote attackers can exploit a path traversal vulnerability in Pichome's textviewer module to read arbitrary files from the server.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Feb 2025
- **Updated:** 27 Feb 2025
- **Also known as:** GHSA-v53m-h2x7-3m5p

## What is CVE-2025-1743?

CVE-2025-1743 is a medium-severity path traversal vulnerability in zyx0814 Pichome, published on 27 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, was found in zyx0814 Pichome 2.1.0. This affects an unknown part of the file /index.php?mod=textviewer. The manipulation of the argument src leads to path traversal. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

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

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


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

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

## Is CVE-2025-1743 being exploited?

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

Public exploit code:

- Pichome 2.1.0 - Arbitrary File Read (nuclei): http/cves/2025/CVE-2025-1743.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1743 is a medium-severity path traversal vulnerability in zyx0814 Pichome, published on 27 Feb 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-1743 exists.

Affected product: zyx0814 Pichome. 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-1743/ (Markdown: https://insights.sbomify.com/CVE-2025-1743/index.md)
```

## Sources

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

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