CVE-2025-56099
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 · uneditedOS Command Injection vulnerability in Ruijie RG-YST AP_3.0(1)B11P280YST250F 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 confidenceOS command injection vulnerability in Ruijie RG-YST AP firmware version 3.0(1)B11P280YST250F allows unauthenticated attackers to execute arbitrary OS commands via a crafted POST request to the pwdmodify function in /usr/lib/lua/luci/modules/common.lua. The application fails to properly sanitize user input before passing it to system shell commands.
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= 3.0\(1\)b11p280yst250f= b11p221= 221= 219= 3.0\(1\)b2p55CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelAccess the device web interface or check the device label/sticker to determine if the model is RG-YST250f, RG-EST310 V2, or RG-EAP602. Alternatively, check the device info page at /cgi-bin/login or similar endpoint.Affected if The device model is one of: RG-YST250f, RG-EST310 V2, or RG-EAP602.
-
Determine firmware versionLog into the device management interface and navigate to System Settings, Status, or About page to view the firmware version. If CLI access is available, use commands like 'show version' or 'system info'.Affected if The firmware version matches: 3.0(1)b11p280yst250f (YST250f), b11p221 (EST310 V2), 221 or 219 (Reyee OS), or 3.0(1)b2p55 (EAP602).
-
Verify pwdmodify endpoint existsSend a probe request to the pwdmodify function endpoint. Based on the path in the CVE, attempt to access /cgi-bin/luci/pwdmodify or check the Lua source at /usr/lib/lua/luci/modules/common.lua if you have shell access.Affected if The pwdmodify function is present in /usr/lib/lua/luci/modules/common.lua and responds to requests.
-
Check management interface exposureDetermine if the device management interface (HTTP/HTTPS on ports 80/443 or custom ports) is directly accessible from the internet or untrusted networks. Use network scanning tools or review firewall rules.Affected if The device management interface is exposed to unauthenticated network access without proper network segmentation.
The environment is affected if the device is a Ruijie RG-YST250f, RG-EST310 V2, or RG-EAP602 running one of the specific firmware versions listed and the management interface is network-accessible.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor patch when available. Immediately restrict network access to the device's management interface and implement input validation/sanitization on the pwdmodify endpoint to prevent shell metacharacter injection.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-56099 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-56099 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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