# CVE-2026-16213: Fantomas42 django-blog-zinnia Protected Entry Password entry_protection.py cleartext storage

> Local attackers can access protected entry passwords stored in cleartext within the django-blog-zinnia plugin, exposing sensitive credentials.

- **Severity:** Medium 4.8 (`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/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-rvxx-mcx2-w53p

## What is CVE-2026-16213?

CVE-2026-16213 is a medium-severity vulnerability in Fantomas42 django-blog-zinnia, published on 19 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information), CWE-310

## Which versions are affected by CVE-2026-16213?


## How do I fix CVE-2026-16213?

No fix has been published for CVE-2026-16213 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-16213 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16213 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-16213 and fix it if it is affected.

What it is: CVE-2026-16213 is a medium-severity vulnerability in Fantomas42 django-blog-zinnia, published on 19 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16213 exists.

Affected product: Fantomas42 django-blog-zinnia. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-16213/ (Markdown: https://insights.sbomify.com/CVE-2026-16213/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16213
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16213
- OSV: https://osv.dev/vulnerability/CVE-2026-16213

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-16213/
Summaries are generated and may contain mistakes; the official description above is the record.