# CVE-2026-124552: Webmin through 2.670 Stored XSS via Shorewall and Shorewall6 list.cgi


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 8 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-6qcf-4v5f-2vjx

## What is CVE-2026-124552?

CVE-2026-124552 is a medium-severity vulnerability in webmin, published on 8 Nov 2026. 

### Official description

Webmin through 2.670 contains a stored cross-site scripting vulnerability in the Shorewall and Shorewall6 modules' list.cgi, which renders table fields and COMMENT lines unescaped. Authenticated users with table edit permission can store JavaScript via savecmt.cgi or table entries that executes when other users, including root, view the list page.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-124552 being exploited?

There is no known exploitation of CVE-2026-124552 in the wild and no public exploit code.

Public exploit code:

- PoC for CVE-2026-124552 — Webmin <= 2.670 stored XSS in Shorewall/Shorewall6 list.cgi leading to RCE as root; includes an unpatched path traversal (arbitrary file write as root) found in the same module (github_poc): https://github.com/googlesky/CVE-2026-124552

## Fix prompt for AI coding agents

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

What it is: CVE-2026-124552 is a medium-severity vulnerability in webmin, published on 8 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124552 in the wild and no public exploit code.

Affected product: webmin. 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-124552/ (Markdown: https://insights.sbomify.com/CVE-2026-124552/index.md)
```

## Sources

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

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