# CVE-2025-2716: China Mobile P22g-CIac Samba Path path traversal

> Remote attackers can exploit a path traversal vulnerability in the Samba Path Handler of China Mobile P22g-CIac devices to access or modify files.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Mar 2025
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-5hrq-c7h5-rwmw

## What is CVE-2025-2716?

CVE-2025-2716 is a medium-severity path traversal vulnerability in China Mobile P22g-CIac, published on 24 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability classified as problematic was found in China Mobile P22g-CIac 1.0.00.488. This vulnerability affects unknown code of the component Samba Path Handler. The manipulation leads to path traversal. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

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


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

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

## Is CVE-2025-2716 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2716 is a medium-severity path traversal vulnerability in China Mobile P22g-CIac, published on 24 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2716 in the wild and no public exploit code.

Affected product: China Mobile P22g-CIac. 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-2716/ (Markdown: https://insights.sbomify.com/CVE-2025-2716/index.md)
```

## Sources

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

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