dbcve.org
Rg Es228gs P FirmwareOperating system · Ruijie

CVE-2025-56752

CRITICAL · 9.4 CVSS v3.1 Published 2025-09-03
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
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
A vulnerability in the Ruijie RG-ES series switch firmware ESW_1.0(1)B1P39 enables remote attackers to fully bypass authentication mechanisms, providing them with unrestricted access to alter administrative settings and potentially seize control of affected devices via crafted HTTP POST request to /user.cgi.

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

The Ruijie RG-ES series switch firmware ESW_1.0(1)B1P39 contains an authentication bypass vulnerability in the web management interface. Attackers can send a crafted HTTP POST request to /user.cgi to completely bypass authentication and gain full administrative access to the device, allowing them to modify settings and potentially take complete control.

MitigationApply the vendor-supplied firmware patch when available; until then, restrict network access to the web management interface using firewall rules or ACLs to prevent unauthorized external access.

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
Rg Es228gs P FirmwareOperating system
Affected:= esw_1.0\(1\)b1p27= esw_1.0\(1\)b1p35= esw_1.0\(1\)b1p39
Rg Es209gc P FirmwareOperating system
Affected:= esw_1.0\(1\)b1p27= esw_1.0\(1\)b1p35= esw_1.0\(1\)b1p39
Rg Es205gc P FirmwareOperating system
Affected:= esw_1.0\(1\)b1p27= esw_1.0\(1\)b1p35= esw_1.0\(1\)b1p39
Rg Es205gc FirmwareOperating system
Affected:= esw_1.0\(1\)b1p27= esw_1.0\(1\)b1p35= esw_1.0\(1\)b1p39
Rg Es208gc FirmwareOperating system
Affected:= esw_1.0\(1\)b1p27= esw_1.0\(1\)b1p35= esw_1.0\(1\)b1p39
Rg Es206gs P FirmwareOperating system
Affected:= esw_1.0\(1\)b1p27= esw_1.0\(1\)b1p35= esw_1.0\(1\)b1p39
Rg Es210gs P FirmwareOperating system
Affected:= esw_1.0\(1\)b1p27= esw_1.0\(1\)b1p35= esw_1.0\(1\)b1p39
Rg Es218gc P FirmwareOperating system
Affected:= esw_1.0\(1\)b1p27= esw_1.0\(1\)b1p35

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
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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
    Access the switch CLI or web interface and retrieve the model name. Look for model numbers: ES228GS, ES209GC, ES205GC, ES208GC, ES206GS, ES210GS, or ES218GC.
    Affected if Device is a Ruijie RG-ES series switch (any of the listed models).
  2. Check installed firmware version
    Log into the switch web interface or CLI and locate the firmware version information. Compare against the affected versions: esw_1.0(1)b1p27, esw_1.0(1)b1p35, or esw_1.0(1)b1p39.
    Affected if Firmware version exactly matches one of the three affected versions listed.
  3. Verify web management interface is enabled
    Check the switch configuration for HTTP/HTTPS web management service status. In CLI, look for commands like 'show running-config' or 'show ip http' to confirm the web interface is active.
    Affected if Web management interface (HTTP on port 80 or HTTPS on port 443) is enabled and reachable.
  4. Confirm /user.cgi endpoint exposure
    From a client on the same network, send a crafted HTTP POST request to http://<device_ip>/user.cgi and observe if authentication is bypassed or if the endpoint responds without credentials.
    Affected if The /user.cgi endpoint responds to POST requests without requiring valid authentication credentials.

User is affected if they have a Ruijie RG-ES series switch (ES228GS, ES209GC, ES205GC, ES208GC, ES206GS, ES210GS, or ES218GC) running firmware version esw_1.0(1)b1p27, esw_1.0(1)b1p35, or esw_1.0(1)b1p39 with the web management interface enabled and exposed.

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

Apply the vendor-supplied firmware patch when available; until then, restrict network access to the web management interface using firewall rules or ACLs to prevent unauthorized external access.

Fix this in Rg Es228gs P Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-56752 — 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-56752 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