Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-11073: Command Injection in Keyfactor RG-EW5100BE

0
Medium
VulnerabilityCVE-2025-11073cvecve-2025-11073
Published: Sat Sep 27 2025 (09/27/2025, 18:02:05 UTC)
Source: CVE Database V5
Vendor/Project: Keyfactor
Product: RG-EW5100BE

Description

A vulnerability was detected in Keyfactor RG-EW5100BE EW_3.0B11P280_EW5100BE-PRO_12183019. The affected element is an unknown function of the file /cgi-bin/luci/api/cmd of the component HTTP POST Request Handler. The manipulation of the argument url results in command injection. The attack can be launched remotely. The exploit is now public and may be used.

AI-Powered Analysis

AILast updated: 10/05/2025, 00:48:35 UTC

Technical Analysis

CVE-2025-11073 is a command injection vulnerability identified in the Keyfactor RG-EW5100BE device, specifically in the firmware version EW_3.0B11P280_EW5100BE-PRO_12183019. The vulnerability resides in an HTTP POST request handler component, within the /cgi-bin/luci/api/cmd endpoint. The flaw arises from improper sanitization or validation of the 'url' argument, which allows an attacker to inject arbitrary commands that the system executes. This vulnerability can be exploited remotely without requiring user interaction or authentication, as indicated by the CVSS vector. The CVSS 4.0 base score is 5.1, categorized as medium severity. The attack vector is network-based (AV:N), with low attack complexity (AC:L), and no privileges required (PR:H indicates high privileges required, but the description and vector seem conflicting; however, the CVSS vector states PR:H, meaning privileges are required, which reduces the risk somewhat). The vulnerability impacts confidentiality, integrity, and availability to a limited extent (VC:L, VI:L, VA:L). There is no scope change or security requirements involved. No patches or mitigations have been published yet, and no known exploits are currently observed in the wild, though a public exploit exists. This vulnerability could allow an attacker to execute arbitrary commands on the device, potentially leading to unauthorized control, data leakage, or disruption of device functionality. Given the device is likely used in network infrastructure or security contexts, exploitation could have broader network implications.

Potential Impact

For European organizations, the impact of this vulnerability could be significant depending on the deployment of the Keyfactor RG-EW5100BE devices within their infrastructure. Since the device appears to be a network or security appliance, successful exploitation could lead to unauthorized command execution, enabling attackers to manipulate device configurations, intercept or redirect network traffic, or disrupt services. This could compromise the confidentiality and integrity of sensitive data and impact availability of critical network functions. Organizations in sectors such as finance, government, healthcare, and critical infrastructure, which rely heavily on secure network devices, could face operational disruptions and data breaches. Furthermore, if these devices are part of a larger security framework, their compromise could serve as a pivot point for lateral movement within corporate networks, increasing the risk of widespread compromise. The medium severity rating suggests a moderate risk, but the lack of authentication requirement for exploitation (if confirmed) elevates the threat level. European entities must assess their exposure based on device usage and firmware versions.

Mitigation Recommendations

Given the absence of official patches, European organizations should immediately inventory their Keyfactor RG-EW5100BE devices and verify firmware versions. If vulnerable versions are detected, organizations should consider the following mitigations: 1) Isolate affected devices from untrusted networks to limit exposure to remote attacks. 2) Implement strict network access controls and firewall rules to restrict access to the /cgi-bin/luci/api/cmd endpoint, allowing only trusted management hosts. 3) Monitor network traffic and device logs for unusual POST requests targeting the vulnerable endpoint, indicating potential exploitation attempts. 4) Disable or restrict the vulnerable API endpoint if possible, or apply custom filtering on input parameters to prevent command injection. 5) Engage with Keyfactor support for guidance and request expedited patch releases. 6) Employ network segmentation to reduce the impact of a compromised device. 7) Prepare incident response plans specifically addressing potential device compromise scenarios. These targeted actions go beyond generic advice by focusing on the specific vulnerable component and attack vector.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-09-26T12:49:32.473Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68d8272cc4b8961499c6ea7e

Added to database: 9/27/2025, 6:04:28 PM

Last enriched: 10/5/2025, 12:48:35 AM

Last updated: 11/10/2025, 7:38:44 AM

Views: 61

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats