Fantomas42 django-blog-zinnia up to 0.20 Protected Entry Password entry_protection.py cleartext storage
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.2 | $0-$5k | 1.09+ |
Summary
A vulnerability classified as problematic has been found in Fantomas42 django-blog-zinnia up to 0.20. Affected by this issue is some unknown functionality of the file zinnia/views/mixins/entry_protection.py of the component Protected Entry Password Handler. This manipulation causes cleartext storage. The identification of this vulnerability is CVE-2026-16213. The attack can only be executed locally. There is no exploit available. The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability has been found in Fantomas42 django-blog-zinnia up to 0.20 and classified as problematic. Affected by this vulnerability is some unknown processing of the file zinnia/views/mixins/entry_protection.py of the component Protected Entry Password Handler. The manipulation with an unknown input leads to a cleartext storage vulnerability. The CWE definition for the vulnerability is CWE-312. The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere. As an impact it is known to affect confidentiality.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-16213. The exploitation appears to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1555 for this issue.
The project was informed of the problem early through an issue report but has not responded yet.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.2
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Cleartext storageCWE: CWE-312 / CWE-310
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
07/18/2026 Advisory disclosed07/18/2026 VulDB entry created
07/18/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 595
Status: Not defined
CVE: CVE-2026-16213 (🔒)
GCVE (CVE): GCVE-0-2026-16213
GCVE (VulDB): GCVE-100-380029
Entry
Created: 07/18/2026 10:57Changes: 07/18/2026 10:57 (55)
Complete: 🔍
Submitter: GalaxynX
Cache ID: 216::103
Submit
Accepted
- Submit #857944: Fantomas42 django-blog-zinnia 881101a9d1d455b2fc581d6f4ae0947cdd8126c6 CWE-312 Cleartext Storage of Sensitive Information (by GalaxynX)
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.