# CVE-2023-44389: Zope management interface vulnerable to stored cross site scripting via the title property

> Attackers can inject malicious scripts into Zope object titles, leading to code execution or account takeover when viewed in the management interface.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Oct 2023
- **Updated:** 27 Nov 2024
- **Also known as:** GHSA-m755-gxxg-r5qh, PYSEC-2023-193

## What is CVE-2023-44389?

CVE-2023-44389 is a low-severity cross-site scripting vulnerability in zopefoundation Zope, published on 4 Oct 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Zope is an open-source web application server. The title property, available on most Zope objects, can be used to store script code that is executed while viewing the affected object in the Zope Management Interface (ZMI). All versions of Zope 4 and Zope 5 are affected. Patches will be released with Zope versions 4.8.11 and 5.8.6.

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

## Which versions are affected by CVE-2023-44389?

5 open source packages ship an affected version, including zope and Zope. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `zope` | PyPI | From 4.0.0 | 4.8.11 |
| `zope` | PyPI | From 5.0 | 5.8.6, 4.8.11 |
| `zope` | PyPI | From 5.0.0 | 5.8.6 |
| `Zope` | PyPI | From 4.0.0 | 4.8.11 |
| `Zope` | PyPI | From 5.0.0 | 5.8.6 |

Products: Zope Zope.

## How do I fix CVE-2023-44389?

Upgrade zope to a fixed version for your release line: 4.8.11 or 5.8.6.

## Is CVE-2023-44389 being exploited?

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

## Other vulnerabilities in zopefoundation Zope

- [CVE-2000-0062](https://insights.sbomify.com/CVE-2000-0062/): Zope DTML implementation Improper Authentication (critical 10.0)
- [CVE-2021-32674](https://insights.sbomify.com/CVE-2021-32674/): Remote Code Execution via traversal in TAL expressions (high 8.8)
- [CVE-2000-1211](https://insights.sbomify.com/CVE-2000-1211/): Zope does not properly perform security registration for legacy names (high 7.5)
- [CVE-2002-0170](https://insights.sbomify.com/CVE-2002-0170/): Zope does not properly verify the access for objects with proxy roles (high 7.5)
- [CVE-2002-0688](https://insights.sbomify.com/CVE-2002-0688/): ZCatalog plug-in for Zope allows anonymous users to bypass access restrictions (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-44389 and fix it if it is affected.

What it is: CVE-2023-44389 is a low-severity cross-site scripting vulnerability in zopefoundation Zope, published on 4 Oct 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-44389 in the wild and no public exploit code.

Affected packages and fixed versions:
- zope (PyPI): affected from 4.0.0; fixed in 4.8.11
- zope (PyPI): affected from 5.0; fixed in 5.8.6, 4.8.11
- zope (PyPI): affected from 5.0.0; fixed in 5.8.6
- Zope (PyPI): affected from 4.0.0; fixed in 4.8.11
- Zope (PyPI): affected from 5.0.0; fixed in 5.8.6

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-2023-44389/ (Markdown: https://insights.sbomify.com/CVE-2023-44389/index.md)
```

## Sources

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

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