dbcve.org
Rg Yst250f FirmwareOperating system · Ruijie

CVE-2025-56113

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-YST EST, YSTAP_3.0(1)B11P280YST250F V1.xxV2.xx allowing attackers to execute arbitrary commands via a crafted POST request to the pwdmodify in file /usr/lib/lua/luci/modules/common.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

OS Command Injection vulnerability in Ruijie RG-YST EST wireless access point firmware. Attackers can execute arbitrary OS commands by sending a crafted POST request to the pwdmodify endpoint in /usr/lib/lua/luci/modules/common.lua, likely due to unsanitized user input being passed to a system call.

MitigationUpdate to vendor-supplied patched firmware when available. As an interim control, restrict network access to the device's management interface to prevent unauthorized attackers from reaching the vulnerable endpoint.

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 the device model
    Access the device's web management interface or CLI and retrieve the model information. This is typically visible on the login page, in System settings, or via 'show version' command via SSH/Telnet.
    Affected if The device is NOT one of: Ruijie RG-YST250f, Ruijie EST310 V2, Ruijie RG-EAP602, or a device running Ruijie Reyee OS (in which case it is not affected)
  2. Check the installed firmware version
    In the web interface, navigate to System or Maintenance settings to find the firmware version. Alternatively, use CLI command 'show version' or 'sysinfo' via SSH/Telnet to retrieve the exact build number.
    Affected if The firmware version matches one of the affected builds: 3.0(1)b11p280yst250f, b11p221, version 221, version 219, or 3.0(1)b2p55
  3. Verify management interface network exposure
    Check which IP addresses can reach the device's HTTP/HTTPS management ports (typically ports 80/443). Use network scanning from an external location or review firewall rules to determine if the management interface is accessible from untrusted networks.
    Affected if The device's web management interface is reachable from network segments that are not trusted or are publicly exposed
  4. Confirm the vulnerable endpoint exists
    Send a POST request to the pwdmodify endpoint. The vulnerable path is /cgi-bin/luci/api/pwdmodify or similar paths under /usr/lib/lua/luci/modules/common.lua. Use curl: curl -X POST http://<device_ip>/cgi-bin/luci/api/pwdmodify
    Affected if The endpoint responds with any HTTP status (200, 400, 401) rather than a connection failure, indicating the vulnerable code path exists on the device

The device is likely affected if it is one of the listed Ruijie models running an affected firmware version and the management interface is accessible to potential attackers.

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

Update to vendor-supplied patched firmware when available. As an interim control, restrict network access to the device's management interface to prevent unauthorized attackers from reaching the vulnerable endpoint.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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