Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2024-27351: In Django 3.2 before 3.2.25, 4.2 before 4.2.11, and 5.0 before 5.0.3, the django.utils.text.Truncator.words() method (with html=True) and…

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.8% (FIRST EPSS); higher than 79.3% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
  • Fixed version: py3-django (Alpine:v3.20) 4.2.11-r0; python-django (Debian:11) 2:2.2.28-1~deb11u7; python-django (Debian:12) 3:3.2.25-0+deb12u1.

Low priority for now. Upgrade to py3-django (Alpine:v3.20) 4.2.11-r0; python-django (Debian:11) 2:2.2.28-1~deb11u7; python-django (Debian:12) 3:3.2.25-0+deb12u1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In Django 3.2 before 3.2.25, 4.2 before 4.2.11, and 5.0 before 5.0.3, the django.utils.text.Truncator.words() method (with html=True) and the truncatewords_html template filter are subject to a potential regular expression denial-of-service attack via a crafted string. NOTE: this issue exists because of an incomplete fix for CVE-2019-14232 and CVE-2023-43665.

MediumCVSS 5.3 · v3.1—No exploit Fix available
Published
Mar 15, 2024
Updated
Jun 17, 2026
EPSS
1.8% · 79th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 1.8%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-27351

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
djangoprojectdjango

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • djangoproject django3.2 and later · before 3.2.25
  • djangoproject django4.2 and later · before 4.2.11
  • djangoproject django5.0 and later · before 5.0.3

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.20py3-djangobefore 4.2.11-r04.2.11-r0
Debian:11python-djangobefore 2:2.2.28-1~deb11u72:2.2.28-1~deb11u7
Debian:12python-djangobefore 3:3.2.25-0+deb12u13:3.2.25-0+deb12u1
Debian:13python-djangobefore 3:4.2.11-13:4.2.11-1
openSUSE:Leap 15.5python-Djangobefore 2.2.28-bp155.7.9.12.2.28-bp155.7.9.1
openSUSE:Leap 15.5python-Djangobefore 2.0.7-150000.1.17.12.0.7-150000.1.17.1
openSUSE:Leap 15.5python-Django1before 1.11.29-bp155.4.9.11.11.29-bp155.4.9.1
openSUSE:Tumbleweedpython-Djangobefore 4.2.11-1.14.2.11-1.1
PyPIdjangofrom 3.2 · before 3.2.253.2.25
PyPIdjangofrom 4.2 · before 4.2.114.2.11
PyPIdjangofrom 5.0 · before 5.0.35.0.3
Red Hat:ansible_automation_platform_developer:2.4::el8python39-blackbefore 0:22.8.0-2.el8ap0:22.8.0-2.el8ap
Red Hat:ansible_automation_platform_developer:2.4::el8python39-cryptographybefore 0:42.0.5-1.el8ap0:42.0.5-1.el8ap
Red Hat:ansible_automation_platform_developer:2.4::el8python39-cryptography-debuginfobefore 0:42.0.5-1.el8ap0:42.0.5-1.el8ap
Red Hat:ansible_automation_platform_developer:2.4::el8python39-idnabefore 0:3.7-1.el8ap0:3.7-1.el8ap
Red Hat:ansible_automation_platform_developer:2.4::el8python39-jinja2before 0:3.1.4-1.el8ap0:3.1.4-1.el8ap
Red Hat:ansible_automation_platform_developer:2.4::el8python39-requestsbefore 0:2.32.2-1.el8ap0:2.32.2-1.el8ap
Red Hat:ansible_automation_platform_developer:2.4::el8python3x-blackbefore 0:22.8.0-2.el8ap0:22.8.0-2.el8ap
Red Hat:ansible_automation_platform_developer:2.4::el8python3x-cryptographybefore 0:42.0.5-1.el8ap0:42.0.5-1.el8ap
Red Hat:ansible_automation_platform_developer:2.4::el8python3x-cryptography-debugsourcebefore 0:42.0.5-1.el8ap0:42.0.5-1.el8ap
Red Hat:ansible_automation_platform_developer:2.4::el8python3x-idnabefore 0:3.7-1.el8ap0:3.7-1.el8ap
Red Hat:ansible_automation_platform_developer:2.4::el8python3x-jinja2before 0:3.1.4-1.el8ap0:3.1.4-1.el8ap
Red Hat:ansible_automation_platform_developer:2.4::el8python3x-requestsbefore 0:2.32.2-1.el8ap0:2.32.2-1.el8ap
Red Hat:ansible_automation_platform_developer:2.4::el8receptorbefore 0:1.4.8-1.el8ap0:1.4.8-1.el8ap

+96

Other highest-scoring records for the same primary product.

  • CVE-2022-34265An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6.
    61This week
  • CVE-2020-7471Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter…
    59Plan
  • CVE-2019-19844Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover.
    55Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-43665Nov 3, 2023 · In Django 3.2 before 3.2.22, 4.1 before 4.1.12, and 4.2 before 4.2.6, the django.utils.text.Truncator chars() and words() methods (when…
    30Monitor
  • ← EarlierCVE-2024-24680Feb 6, 2024 · An issue was discovered in Django 3.2 before 3.2.24, 4.2 before 4.2.10, and Django 5.0 before 5.0.2.
    30Monitor
  • Later →CVE-2024-38875Jul 10, 2024 · An issue was discovered in Django 4.2 before 4.2.14 and 5.0 before 5.0.7.
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:py3-django4.2.11-r0 · Alpine:v3.20Package registry (OSV)
debian:python-django3:3.2.25-0+deb12u1 · Debian:12Package registry (OSV)
opensuse:python-Django2.0.7-150000.1.17.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:python-Django2.2.28-bp155.7.9.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:python-Django11.11.29-bp155.4.9.1 · openSUSE:Leap 15.5Package registry (OSV)
PyPI:django3.2.25Package registry (OSV)
PyPI:django4.2.11Package registry (OSV)
PyPI:django5.0.3Package registry (OSV)
red hat:automation-controller-venv-tower0:4.5.5-2.el8ap · Red Hat:ansible_automation_platform:2.4::el8Package registry (OSV)
red hat:python-aiohttp0:3.9.3-1.el9ap · Red Hat:ansible_automation_platform:2.4::el9Package registry (OSV)
red hat:python-aiohttp-debugsource0:3.9.3-1.el9ap · Red Hat:ansible_automation_platform:2.4::el9Package registry (OSV)
red hat:python3-aiohttp0:3.9.3-1.el9ap · Red Hat:ansible_automation_platform:2.4::el9Package registry (OSV)
red hat:python3-aiohttp-debuginfo0:3.9.3-1.el9ap · Red Hat:ansible_automation_platform:2.4::el9Package registry (OSV)
red hat:python39-aiohttp0:3.9.3-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8Package registry (OSV)
red hat:python39-aiohttp-debuginfo0:3.9.3-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8Package registry (OSV)
red hat:python39-django0:4.2.11-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8Package registry (OSV)
red hat:python3x-aiohttp0:3.9.3-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8Package registry (OSV)
red hat:python3x-aiohttp-debugsource0:3.9.3-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8Package registry (OSV)
red hat:receptor0:1.4.5-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8Package registry (OSV)
red hat:receptorctl0:1.4.5-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8Package registry (OSV)
suse:python-Django1.11.29-3.59.3 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:python-Django2.2.28-bp155.7.9.1 · SUSE:Package Hub 15 SP5Package registry (OSV)
suse:python-Django11.11.29-3.58.3 · SUSE:OpenStack Cloud 9Package registry (OSV)
suse:python-Django11.11.29-bp155.4.9.1 · SUSE:Package Hub 15 SP5Package registry (OSV)
suse:venv-openstack-horizon14.1.1~dev11-4.51.4 · SUSE:OpenStack Cloud 9Package registry (OSV)
suse:venv-openstack-horizon-hpe12.0.5~dev6-14.54.4 · SUSE:HPE Helion OpenStack 8Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2023-36053256 days apartIn Django 3.2 before 3.2.20, 4 before 4.1.10, and 4.2 before 4.2.3, EmailValidator and URLValidator are subject to a potential ReDoS…
    31Monitor
  • CVE-2022-41323516 days apartIn Django 3.2 before 3.2.16, 4.0 before 4.0.8, and 4.1 before 4.1.2, internationalized URLs were subject to a potential denial of service…
    31Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records