Summary
SVG with embedded scripts can lead to cross-site scripting attacks in xml2rfc
xml2rfc allows script elements in SVG sources.
In HTML output having these script elements can lead to XSS attacks.
Sample XML snippet:
<artwork type="svg" src="data:image/svg+xml,%3Csvg viewBox='0 0 10 10' xmlns='http://www.w3.org/2000/svg'%3E%3Cscript%3E window.alert('Test Alert'); %3C/script%3E%3C/svg%3E">
</artwork>
Workarounds
If SVG source is self-contained within the XML, scraping script elements from SVG files.
References
For more information
If you have any questions or comments about this advisory:
- Open an issue in xml2rfc
- Email us at [email protected]
- Infrastructure and Services Vulnerability Disclosure
Impact
This vulnerability impacts website that publish HTML drafts and RFCs.
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
This has been fixed in version 3.12.4.
Frequently Asked Questions
- What is GHSA-CF4Q-4CQR-7G7W? GHSA-CF4Q-4CQR-7G7W is a medium-severity cross-site scripting (XSS) vulnerability in xml2rfc (pip), affecting versions < 3.12.4. It is fixed in 3.12.4. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- Which versions of xml2rfc are affected by GHSA-CF4Q-4CQR-7G7W? xml2rfc (pip) versions < 3.12.4 is affected.
- Is there a fix for GHSA-CF4Q-4CQR-7G7W? Yes. GHSA-CF4Q-4CQR-7G7W is fixed in 3.12.4. Upgrade to this version or later.
- Is GHSA-CF4Q-4CQR-7G7W exploitable, and should I be worried? Whether GHSA-CF4Q-4CQR-7G7W is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-CF4Q-4CQR-7G7W is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-CF4Q-4CQR-7G7W? Upgrade
xml2rfcto 3.12.4 or later.