dbcve.org
Rg Yst250f FirmwareOperating system · Ruijie

CVE-2025-56084

HIGH · 8.8 CVSS v3.1 Published 2025-12-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
OS Command Injection vulnerability in Ruijie RG-EW1800GX PRO B11P226_EW1800GX-PRO_10223117 allowing attackers to execute arbitrary commands via a crafted POST request to the module_set in file /usr/local/lua/dev_sta/nbr_cwmp.lua.

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 an OS command injection vulnerability in the Ruijie RG-EW1800GX PRO router's web interface. The vulnerability exists in the module_set parameter of the POST request handler in /usr/local/lua/dev_sta/nbr_cwmp.lua. Attackers can inject and execute arbitrary OS commands by submitting specially crafted requests, potentially gaining full control of the device with root privileges.

MitigationApply vendor firmware updates when available. Until then, restrict access to the device's web management interface to trusted IP addresses only, or disable the affected TR-069/CWMP service if not required.

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 Yst250f FirmwareOperating system
Affected:= 3.0\(1\)b11p280yst250f
Rg Est310 V2 FirmwareOperating system
Affected:= b11p221
Reyee OsOperating system
Affected:= 221= 219
Rg Eap602 FirmwareOperating system
Affected:= 3.0\(1\)b2p55

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 router's web interface or use SNMP/SSH to query the device and retrieve the model name and firmware version. Compare against the affected versions: Ruijie Rg Yst250f (3.0(1)b11p280yst250f), Ruijie Rg Est310 V2 (b11p221), Ruijie Reyee Os (221, 219), Ruijie Rg Eap602 (3.0(1)b2p55).
    Affected if The device model matches one of the listed products and the firmware version matches the specific versions provided.
  2. Verify the web management interface is accessible
    Attempt to reach the device's HTTP/HTTPS web interface on the expected management port (typically 80 or 443).
    Affected if The web interface responds and accepts authentication, indicating it is exposed.
  3. Check if CWMP/TR-069 service is enabled
    Log into the router administration panel and navigate to the TR-069 or CWMP settings page (usually under Advanced Settings, Network, or Management). Look for options labeled TR-069, CWMP, ACS, or Auto Configuration. Alternatively, probe common TR-069 ports (7547 or 8080) or check the nbr_cwmp.lua file on the device filesystem if you have SSH/Telnet access.
    Affected if The CWMP/TR-069 service is enabled and the device is configured to accept CWMP requests.
  4. Inspect the vulnerable lua script
    If you have shell access (via SSH/Telnet), check for the existence and permissions of /usr/local/lua/dev_sta/nbr_cwmp.lua. This file handles the module_set parameter in POST requests.
    Affected if The file /usr/local/lua/dev_sta/nbr_cwmp.lua exists and is executable by the web service user.

A defender is affected if they are running one of the specific Ruijie firmware versions listed AND the device's web management interface is accessible with CWMP/TR-069 enabled, allowing attackers to inject commands via the module_set parameter in the nbr_cwmp.lua handler.

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 vendor firmware updates when available. Until then, restrict access to the device's web management interface to trusted IP addresses only, or disable the affected TR-069/CWMP service if not required.

Fix this in Rg Yst250f Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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