# CVE-2019-16935: Cross-site scripting in n/a > Attackers can execute arbitrary JavaScript in clients visiting the XML-RPC server if the server title is set with untrusted input. - **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 28 Sep 2019 - **Updated:** 7 Oct 2026 - **Also known as:** ALPINE-CVE-2019-16935, CLEANSTART-2026-QJ43408, DEBIAN-CVE-2019-16935, GHSA-qhmv-wcg2-h8hx, PSF-2019-6, RHSA-2020:3911, UBUNTU-CVE-2019-16935 ## What is CVE-2019-16935? CVE-2019-16935 is a medium-severity cross-site scripting vulnerability in Canonical Ubuntu Linux, published on 28 Sep 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description The documentation XML-RPC server in Python through 2.7.16, 3.x through 3.6.9, and 3.7.x through 3.7.4 has XSS via the server_title field. This occurs in Lib/DocXMLRPCServer.py in Python 2.x, and in Lib/xmlrpc/server.py in Python 3.x. If set_server_title is called with untrusted input, arbitrary JavaScript can be delivered to clients that visit the http URL for this server. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2019-16935? It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `python` | Red Hat:enterprise_linux:7::client | All versions | 0:2.7.5-89.el7 | | `python-debug` | Red Hat:enterprise_linux:7::client | All versions | 0:2.7.5-89.el7 | | `python-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:2.7.5-89.el7 | | `python-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:2.7.5-89.el7 | | `python-libs` | Red Hat:enterprise_linux:7::client | All versions | 0:2.7.5-89.el7 | | `python-test` | Red Hat:enterprise_linux:7::client | All versions | 0:2.7.5-89.el7 | | `python-tools` | Red Hat:enterprise_linux:7::client | All versions | 0:2.7.5-89.el7 | | `tkinter` | Red Hat:enterprise_linux:7::client | All versions | 0:2.7.5-89.el7 | | `python` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.7.5-89.el7 | | `python-debug` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.7.5-89.el7 | | `python-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.7.5-89.el7 | | `python-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.7.5-89.el7 | | `python-libs` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.7.5-89.el7 | | `python-test` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.7.5-89.el7 | | `python-tools` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.7.5-89.el7 | | `tkinter` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.7.5-89.el7 | | `python` | Red Hat:enterprise_linux:7::server | All versions | 0:2.7.5-89.el7 | | `python-debug` | Red Hat:enterprise_linux:7::server | All versions | 0:2.7.5-89.el7 | | `python-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:2.7.5-89.el7 | | `python-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:2.7.5-89.el7 | | `python-libs` | Red Hat:enterprise_linux:7::server | All versions | 0:2.7.5-89.el7 | | `python-test` | Red Hat:enterprise_linux:7::server | All versions | 0:2.7.5-89.el7 | | `python-tools` | Red Hat:enterprise_linux:7::server | All versions | 0:2.7.5-89.el7 | | `tkinter` | Red Hat:enterprise_linux:7::server | All versions | 0:2.7.5-89.el7 | | `python` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.7.5-89.el7 | | `python-debug` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.7.5-89.el7 | | `python-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.7.5-89.el7 | | `python-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.7.5-89.el7 | | `python-libs` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.7.5-89.el7 | | `python-test` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.7.5-89.el7 | | `python-tools` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.7.5-89.el7 | | `tkinter` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.7.5-89.el7 | Products: Canonical Ubuntu Linux, Debian Debian Linux, Python Python. ## How do I fix CVE-2019-16935? Upgrade to a fixed version. ## Is CVE-2019-16935 being exploited? There is no known exploitation of CVE-2019-16935 in the wild and no public exploit code. ## Other vulnerabilities in Canonical Ubuntu Linux - [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild) - [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-16935 and fix it if it is affected. What it is: CVE-2019-16935 is a medium-severity cross-site scripting vulnerability in Canonical Ubuntu Linux, published on 28 Sep 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2019-16935 in the wild and no public exploit code. Affected product: Canonical Ubuntu Linux. 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-2019-16935/ (Markdown: https://insights.sbomify.com/CVE-2019-16935/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-16935 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-16935 - OSV: https://osv.dev/vulnerability/CVE-2019-16935 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-16935/ Summaries are generated and may contain mistakes; the official description above is the record.