# CVE-2025-60262: Misconfiguration in n/a

> Remote attackers can gain root control by uploading files via anonymous FTP due to a vsftpd misconfiguration on H3C wireless devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jan 2026
- **Updated:** 6 Jan 2026
- **Also known as:** GHSA-r36f-vrxf-7jf9

## What is CVE-2025-60262?

CVE-2025-60262 is a critical vulnerability in n/a, published on 6 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in H3C M102G HM1A0V200R010 wireless controller and BA1500L SWBA1A0V100R006 wireless access point, there is a misconfiguration vulnerability about vsftpd. Through this vulnerability, all files uploaded anonymously via the FTP protocol is automatically owned by the root user and remote attackers could gain root-level control over the devices.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 2 products.


Products: H3c Magic Ba1500l Firmware, H3c Mc102-G Firmware.

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

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

## Is CVE-2025-60262 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60262 is a critical vulnerability in n/a, published on 6 Jan 2026. 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-60262 exists.

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

## Sources

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

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