# CVE-2024-58396: YouDataSum CPAS Audit Management System V4 Path Traversal via downPlugs fileId


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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-h4xq-5878-6xvr

## What is CVE-2024-58396?

CVE-2024-58396 is a high-severity vulnerability in YouDataSum CPAS Audit Management System, published on 22 Oct 2026. 

### Official description

YouDataSum CPAS Audit Management System V4 contains a path traversal vulnerability that allows unauthenticated attackers to read arbitrary files by manipulating the fileId parameter. Attackers can send GET requests to /cpasm4/plugInManController/downPlugs with ../ sequences in fileId to retrieve system files like /etc/passwd. Exploitation evidence was first observed by the Shadowserver Foundation on 2025-01-13.

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

## Which versions are affected by CVE-2024-58396?


## How do I fix CVE-2024-58396?

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

## Is CVE-2024-58396 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-58396 and fix it if it is affected.

What it is: CVE-2024-58396 is a high-severity vulnerability in YouDataSum CPAS Audit Management System, published on 22 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-58396 exists.

Affected product: YouDataSum CPAS Audit Management System. 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-2024-58396/ (Markdown: https://insights.sbomify.com/CVE-2024-58396/index.md)
```

## Sources

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

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