dbcve.org
Mc102 G FirmwareOperating system · H3c

CVE-2025-60262

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a vsftpd misconfiguration on H3C wireless controllers and access points where anonymous FTP uploads result in files being owned by the root user instead of the ftp user. This allows remote unauthenticated attackers to potentially write malicious files with root ownership, achieving arbitrary code execution with root privileges.

MitigationDisable anonymous FTP access in vsftpd configuration and ensure uploaded files are owned by a non-privileged service account. If FTP is not required, disable the vsftpd service entirely.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mc102 G FirmwareOperating system
Affected:= hm1a0v200r010
Magic Ba1500l FirmwareOperating system
Affected:= swba1a0v100r006

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model and firmware version
    Access the device CLI or web interface and retrieve the model name and firmware version. For CLI, typical commands include 'display version' or 'show system-info'. For web interface, check the status or management page.
    Affected if The device is an H3C MC102G running firmware hm1a0v200r010, or an H3C Magic BA1500L running firmware swba1a0v100r006.
  2. Verify vsftpd service is running
    Check if the vsftpd daemon is active on the device. In the device CLI, use commands like 'display vsftpd status' or check running processes via 'display process vsftpd' if available.
    Affected if vsftpd is enabled and running on the device.
  3. Check anonymous FTP access configuration
    Inspect the vsftpd configuration file (typically /etc/vsftpd.conf or /etc/vsftpd/vsftpd.conf on the device). Look for the 'anonymous_enable' setting.
    Affected if anonymous_enable is set to YES, allowing anonymous FTP logins.
  4. Check anonymous upload permissions
    In the vsftpd configuration file, verify the 'anon_upload_enable' setting. Also check for 'anon_mkdir_write_enable' if present.
    Affected if anon_upload_enable is set to YES, permitting anonymous users to upload files.
  5. Verify file ownership on uploaded files
    If anonymous FTP is enabled, attempt a test upload (in a safe lab environment) or examine the vsftpd configuration for 'anon_root' and 'listen' settings. Check the owner of existing uploaded files in the FTP directory.
    Affected if Uploaded files are owned by root instead of the ftp user or a non-privileged service account.

The environment is affected if it is an H3C MC102G or Magic BA1500L on the specified firmware versions, with vsftpd running and anonymous FTP upload enabled, where uploaded files become root-owned instead of being owned by a non-privileged user.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable anonymous FTP access in vsftpd configuration and ensure uploaded files are owned by a non-privileged service account. If FTP is not required, disable the vsftpd service entirely.

Fix this in Mc102 G Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-60262 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-60262 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data