# CVE-2022-51025: Penta Security WAPPLES 4.0.54.1 / 5.0 / 6.0 Path Traversal via /webapi/file/transfer


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-5wwc-x9f3-f86v

## What is CVE-2022-51025?

CVE-2022-51025 is a high-severity vulnerability in Penta Security Systems WAPPLES, published on 22 Oct 2026. 

### Official description

Penta Security WAPPLES 4.0.54.1, 5.0, and 6.0 contains a path traversal vulnerability that allows authenticated attackers to download arbitrary files via the name parameter of /webapi/file/transfer. Attackers can send GET requests with type=db_backup and ../ sequences in name to read files like /etc/passwd, and a hardcoded systemi account makes authentication effectively trivial. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-19.

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

## Which versions are affected by CVE-2022-51025?


## How do I fix CVE-2022-51025?

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

## Is CVE-2022-51025 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-51025 and fix it if it is affected.

What it is: CVE-2022-51025 is a high-severity vulnerability in Penta Security Systems WAPPLES, published on 22 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-51025 exists.

Affected product: Penta Security Systems WAPPLES. 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-2022-51025/ (Markdown: https://insights.sbomify.com/CVE-2022-51025/index.md)
```

## Sources

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

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