Approved changes feed: RSS · Atom

cpe:2.3:a:djangoblog_project:djangoblog:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorDjangoblog Project (7b0eef06-885d-5b5c-853a-474c3c01186b)
ProductDjangoblog (d3110542-73bb-5239-97ea-2ba90dbf34de)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2023-2954 vulnerable 2026-06-08 06:02:43.700580 Cross-site Scripting (XSS) - Stored in liangliangyy/djangoblog
MEDIUM (4.8)
Cross-site Scripting (XSS) - Stored in GitHub repository liangliangyy/djangoblog prior to master.
Published: 2023-05-29T00:00:00.000Z
Updated: 2025-01-13T21:02:16.160Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2019-14232 vulnerable 2026-06-08 05:12:54.298185 Details available
An issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4. If django.utils.text.Truncator's chars() and words() methods were passed the html=True argument, they were extremely slow to evaluate certain inputs due to a catastrophic backtracking vulnerability in a regular expression. The chars() and words() methods are used to implement the truncatechars_html and truncatewords_html template filters, which were thus vulnerable.
Published: 2019-08-02T00:00:00.000Z
Updated: 2024-08-05T00:12:42.892Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.