# CVE-2025-30014: Directory Traversal vulnerability in SAP Capital Yield Tax Management

> An attacker with low privileges can read unauthorized files due to insufficient path validation in SAP Capital Yield Tax Management.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2025
- **Updated:** 8 Apr 2025
- **Also known as:** GHSA-6whq-cc4j-9xc8

## What is CVE-2025-30014?

CVE-2025-30014 is a high-severity path traversal vulnerability in SAP_SE SAP Capital Yield Tax Management, published on 8 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SAP Capital Yield Tax Management has directory traversal vulnerability due to insufficient path validation. This could allow an attacker with low privileges to read files from directory which they don�t have access to, hence causing a high impact on confidentiality. Integrity and Availability are not affected.

Weakness: CWE-35 (Path Traversal: '.../...//')

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


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

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

## Is CVE-2025-30014 being exploited?

There is no known exploitation of CVE-2025-30014 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30014 is a high-severity path traversal vulnerability in SAP_SE SAP Capital Yield Tax Management, published on 8 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-30014 in the wild and no public exploit code.

Affected product: SAP_SE SAP Capital Yield Tax Management. 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-30014/ (Markdown: https://insights.sbomify.com/CVE-2025-30014/index.md)
```

## Sources

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

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