CVE-2022-28108 — selenium-grid
HIGHCVE-2022-28108 is a high-severity (CVSS 8.8) Cross-Site Request Forgery (CSRF) vulnerability in org.seleniumhq.selenium:selenium-grid. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.seleniumhq.selenium:selenium-grid — see the affected versions and patch details below.
Selenium Server (Grid) CSRF
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.seleniumhq.selenium:selenium-grid☕org.seleniumhq.selenium:selenium-serverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.seleniumhq.selenium:selenium-grid | all versions | 4.0.0-alpha-7org.seleniumhq.selenium:selenium-grid:4.0.0-alpha-7 |
| ☕Maven | org.seleniumhq.selenium:selenium-server | all versions | No fix |
Affected Products
selenium gridseleniumResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.seleniumhq.selenium:selenium-grid, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.seleniumhq.selenium:selenium-grid to 4.0.0-alpha-7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-28108 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How to detect CVE-2022-28108
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2022-28108 -u https://target- Template
- Selenium Grid < 4.0.0-alpha-7 - Remote Code Execution
- Severity
- critical
- Impact
- An unauthenticated attacker can achieve remote code execution as the Selenium Grid process owner by crafting a malicious payload and sending it to the /wd/hub/session endpoint.
- Remediation
- Upgrade to Selenium Server 4.0.0-alpha-7 or later and restrict network exposure.
Template by ProjectDiscovery nuclei-templates (t0xk), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2022-28108 in your dependencies?
Find it across Maven, including transitive dependencies.