Black Friday60% off BLACKFRIDAY2026
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
critical·Product Based Web Vulnerabilities·Updated Nov 9, 2026

CVE-2022-28108 Scanner

CVE-2022-28108 Scanner - Remote Code Execution vulnerability in Selenium Grid

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsurl
CostFree
5
Times Used
continuous scan runs
4.2k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
8.8
CVSS
Description

Selenium Server (Grid) before 4 allows CSRF because it permits non-JSON content types such as application/x-www-form-urlencoded, multipart/form-data, and text/plain.

Attack Vector
-
Privileges Req.
-
User Interaction
-
Affected
n/aby n/a
n/a
Updated Nov 7, 2026View on NVD →
Detail

Selenium Grid is primarily used by developers and testers who require the ability to run tests on multiple machines and browsers simultaneously. The software facilitates the efficient distribution of test execution by providing a hub and node architecture, making it popular in the quality assurance processes of web application development. It's widely adopted in automated testing frameworks for its capability to run parallel tests, saving time and resources. The open-source nature of Selenium Grid allows organizations to customize and extend its functionalities according to their specific needs. It finds application in both small-scale projects and large enterprises due to its robust features and support for various environments. Selenium Grid enables testers to achieve a high level of accuracy in cross-browser testing.

The vulnerability discussed here allows for remote code execution within versions of Selenium Grid prior to 4.0.0-alpha-7. This security flaw arises due to missing origin validation and weak content-type enforcement in the software's handling of session creation, particularly at the /wd/hub/session endpoint. Remote attackers can leverage this vulnerability by injecting malicious payloads without the need to authenticate, potentially taking control of the affected machine. The weakness affects any application leveraging the vulnerable version of Selenium Grid, particularly compromising systems that have exposed the Selenium Grid endpoint to the network. This issue is cataloged under CVE-2022-28108 and deemed critical due to its impact and ease of exploitation. The vulnerability represents a significant threat as it allows attackers to manipulate sessions and execute arbitrary commands.

The technical details of this weakness reveal that the /wd/hub/session endpoint doesn't properly validate the origin of requests or adequately enforce content types, making it susceptible to exploitation. Attackers can craft specific POST requests designed to inject capabilities with unsafe options that facilitate the execution of arbitrary commands. This can include command line utilities that interact with the operating system, such as launching a ping command to an external server. The use of DNS rebinding techniques further amplifies the risk, enabling attackers to bypass network restrictions and interact directly with the vulnerable endpoint. The default configurations of Selenium Grid may inadequately protect against such malicious input, necessitating immediate patches or network restriction measures. Additionally, awareness of these technical loopholes allows developers and security personnel to craft better defenses and apply patches effectively.

The potential effects of exploiting this vulnerability include unauthorized remote command execution, potentially leading to full control over the Selenium Grid server. An attacker could install malicious software, extract sensitive data, or deploy subsequent attacks from the compromised server. The compromise of this nature could disrupt business operations, particularly in environments heavily relying on automated browser tests that leverage Selenium Grid. There is also a significant risk of data leakage if attackers use the server to pivot and explore accessible network resources. The remediation of this vulnerability involves upgrading to a secured version and applying proper network restrictions to reduce the attack surface. The timely address of this security gap is essential to prevent potential exploitation and maintain the integrity of the testing environment.

REFERENCES

Solution Advice
  • Upgrade to Selenium Server 4.0.0-alpha-7 or later to ensure the vulnerability is patched.
  • Restrict network exposure of the Selenium Grid by implementing proper firewall rules.
  • Regularly audit and monitor network traffic to the Selenium Grid for any unusual activity.
  • Implement strong origin validation and content-type enforcement where possible.
  • Backup systems regularly to ensure data integrity and quick recovery in case of an attack.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

12,000+ scanners. Free to start. No credit card required.