Is CVE-2024-11319 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2024-11319 being exploited in the wild.

How severe is CVE-2024-11319?

Medium severity, with a CVSS score of 5.5, published 18 November 2024.

Which products and versions are affected?

django-cms (PyPI) ECOSYSTEM:introduced=3.11.7,fixed=3.11.9, GIT:introduced=0,fixed=241d1cbe47a68f5d271ce4d27ad5e32e2c360ec3|ECOSYSTEM:introduced=0.

Is there a fix for CVE-2024-11319?

Yes. django-cms (PyPI): upgrade to 3.11.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2024-11319 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2024-11319?

Check whether you run django-cms (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2024-11319: django CMS stored XSS in Page Title field

CVE-2024-11319 · Severity: medium · CVSS 5.5 · Published 2024-11-18

django CMS is a popular open-source content management system used to build and manage websites. A security flaw in the page creation interface allows users with high-level administrative privileges to inject malicious scripts into page titles. If exploited, these scripts could execute in the browsers of other users or administrators, potentially leading to unauthorized actions or data theft within the management console.

Technologies: django-cms (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2024-11319 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2024-11319 being exploited in the wild.
How severe is CVE-2024-11319?: Medium severity, with a CVSS score of 5.5, published 18 November 2024.
Which products and versions are affected?: django-cms (PyPI) ECOSYSTEM:introduced=3.11.7,fixed=3.11.9, GIT:introduced=0,fixed=241d1cbe47a68f5d271ce4d27ad5e32e2c360ec3|ECOSYSTEM:introduced=0.
Is there a fix for CVE-2024-11319?: Yes. django-cms (PyPI): upgrade to 3.11.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2024-11319 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2024-11319?: Check whether you run django-cms (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

django-cms (PyPI): upgrade to 3.11.9 or later
```
pip install "django-cms>=3.11.9"
```

Technical details

A stored Cross-Site Scripting (XSS) vulnerability exists in django CMS versions 3.11.7, 3.11.8, 4.1.2, and 4.1.3. The flaw is located in the Page Title field of the Page Creation interface at the /admin/cms/pagecontent/ endpoint. Due to improper neutralization of input during web page generation, an attacker with high privileges (PR:H) can inject malicious scripts that are subsequently rendered and executed in the context of other users' sessions. The issue has been addressed in versions 3.11.9 and 4.1.4.

Affected products

django CMS Association django-cms >= 3.11.7, < 3.11.9
django CMS Association django-cms >= 4.1.2, < 4.1.4

Identifiers

CVE-2024-11319
GHSA-gv5h-5655-h4mv
PYSEC-2024-124

Timeline

2024-11-13: advisory: Vendor security update published
2024-11-18: disclosed: CVE-2024-11319 published
2024-11-18: patched: GitHub advisory reviewed and patched versions confirmed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.