CVE-2023-42458

Zope vulnerable to Stored Cross Site Scripting with SVG images

Workarounds

Make sure the "Add Documents, Images, and Files" permission is only assigned to trusted roles. By default only the Manager has this permission.

There is a stored cross site scripting vulnerability for SVG images.

Note that an image tag with an SVG image as source is never vulnerable, even when the SVG image contains malicious code. To exploit the vulnerability, an attacker would first need to upload an image, and then trick a user into following a specially crafted link.

All versions of Zope are impacted on sites that allow untrusted users to upload images.

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.

CVE-2023-42458 has a CVSS score of 3.7 (Low). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.8.10, 5.8.5); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Patches will be released in Zope 4.8.10 and 5.8.5.

1. What is CVE-2023-42458? CVE-2023-42458 is a low-severity cross-site scripting (XSS) vulnerability in Zope (pip), affecting versions <= 4.8.9. It is fixed in 4.8.10, 5.8.5. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2023-42458? CVE-2023-42458 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of Zope are affected by CVE-2023-42458? Zope (pip) versions <= 4.8.9 is affected.
4. Is there a fix for CVE-2023-42458? Yes. CVE-2023-42458 is fixed in 4.8.10, 5.8.5. Upgrade to this version or later.
5. Is CVE-2023-42458 exploitable, and should I be worried? Whether CVE-2023-42458 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
6. What actually determines whether CVE-2023-42458 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.
7. How do I fix CVE-2023-42458?
   • Upgrade Zope to 4.8.10 or later
   • Upgrade Zope to 5.8.5 or later

Other vulnerabilities in Zope