cve.bz

CVE-2026-16213 fantomas42 django-blog-zinnia: Cryptographic Issues

4.8 mediumEPSS 0.1%

Medium (4.8) in fantomas42 django-blog-zinnia. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
A security flaw has been discovered in Fantomas42 django-blog-zinnia up to 0.20. Affected by this vulnerability is an unknown functionality of the file zinnia/views/mixins/entry_protection.py of the component Protected Entry Password Handler. The manipulation results in cleartext storage of sensitive information. The attack needs to be approached locally. The project was informed of the problem early through an issue report but has not responded yet.

Severity

CVSS 4.0

4.8 medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

3.3 low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-07-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-310 Cryptographic Issues
CWE-312 Cleartext Storage of Sensitive Information
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-16213 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-16213?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-16213?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-16213 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Fantomas42 django-blog-zinnia0.1
Fantomas42 django-blog-zinnia0.2
Fantomas42 django-blog-zinnia0.3
Fantomas42 django-blog-zinnia0.4
Fantomas42 django-blog-zinnia0.5
Fantomas42 django-blog-zinnia0.6
Fantomas42 django-blog-zinnia0.7
Fantomas42 django-blog-zinnia0.8
Fantomas42 django-blog-zinnia0.9
Fantomas42 django-blog-zinnia0.10
Fantomas42 django-blog-zinnia0.11
Fantomas42 django-blog-zinnia0.12
Fantomas42 django-blog-zinnia0.13
Fantomas42 django-blog-zinnia0.14
Fantomas42 django-blog-zinnia0.15
Fantomas42 django-blog-zinnia0.16
Fantomas42 django-blog-zinnia0.17
Fantomas42 django-blog-zinnia0.18
Fantomas42 django-blog-zinnia0.19
Fantomas42 django-blog-zinnia0.20

Attack patterns (CAPEC)

  • CAPEC-37 Retrieve Embedded Sensitive Data Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON