CVE-2025-56099
BaseFortify
Publication date: 2025-12-11
Last updated on: 2026-02-11
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ruijie | rg-yst250f_firmware | 3.0(1)b11p280yst250f |
| ruijie | rg-est310_v2_firmware | b11p221 |
| ruijie | reyee_os | 221 |
| ruijie | reyee_os | 219 |
| ruijie | rg-eap602_firmware | 3.0(1)b2p55 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-78 | The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection can be performed by monitoring for crafted POST requests targeting the pwdmodify endpoint in the /usr/lib/lua/luci/modules/common.lua file. Network traffic inspection tools can be used to identify unusual POST requests to this endpoint. Specific commands are not provided in the available resources. [1]
Can you explain this vulnerability to me?
This vulnerability is an OS Command Injection in Ruijie RG-YST AP_3.0(1)B11P280YST250F. It allows attackers to execute arbitrary operating system commands by sending a specially crafted POST request to the pwdmodify function in the file /usr/lib/lua/luci/modules/common.lua.
How can this vulnerability impact me? :
An attacker exploiting this vulnerability can execute arbitrary commands on the affected device, potentially leading to unauthorized access, data compromise, device control, or disruption of services.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps are not explicitly detailed in the provided resources. Generally, restricting access to the vulnerable endpoint, applying any available patches or updates from the vendor, and monitoring for suspicious activity are recommended. [1]