Django Unicorn
Approved changes feed: RSS · Atom
cpe:2.3:a:django-commons:django-unicorn:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Django Commons (2dc58eb5-47c3-53b5-8f62-44ebea19f524) |
|---|---|
| Product | Django Unicorn (269aff3c-18ab-5a7a-a858-e6ff6f1a9cdf) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-31815 |
vulnerable | 2026-06-08 07:57:15.924147 |
django-unicorn affected by component state manipulation via unvalidated attribute access
MEDIUM (5.3)
Unicorn adds modern reactive component functionality to your Django templates. Prior to 0.67.0, component state manipulation is possible in django-unicorn due to missing access control checks during property updates and method calls. An attacker can bypass the intended _is_public protection to modify internal attributes such as template_name or trigger protected methods. This vulnerability is fixed in 0.67.0.
Published: 2026-03-10T21:07:08.198Z
Updated: 2026-03-11T14:18:26.595Z |
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 this panel to browse, search, copy or download the JSON record.