# CVE-2026-120242: Ruijie RG-ES205GC Cloud Management set_cloud_serverUrl.cgi cross site scripting


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 1 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-7mq6-x8qc-4qch

## What is CVE-2026-120242?

CVE-2026-120242 is a medium-severity vulnerability in Ruijie RG-ES205GC, published on 1 Nov 2026. 

### Official description

A security flaw has been discovered in Ruijie RG-ES205GC, RG-ES206GC-P, RG-ES208GC, RG-ES210GC-LP and RG-ES210GS-P ESW_1.0(1)B1P48. The affected element is an unknown function of the file set_cloud_serverUrl.cgi of the component Cloud Management. The manipulation of the argument url results in cross site scripting. It is possible to launch the attack remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-120242?


## How do I fix CVE-2026-120242?

No fix has been published for CVE-2026-120242 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-120242 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120242 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120242 and fix it if it is affected.

What it is: CVE-2026-120242 is a medium-severity vulnerability in Ruijie RG-ES205GC, published on 1 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120242 exists.

Affected product: Ruijie RG-ES205GC. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120242/ (Markdown: https://insights.sbomify.com/CVE-2026-120242/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120242
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120242
- OSV: https://osv.dev/vulnerability/CVE-2026-120242

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120242/
Summaries are generated and may contain mistakes; the official description above is the record.
