PatchTheCVECVE-2022-1780: The LaTeX for WordPress plugin through 3.4.10 does not have CSRF check in place when updating its settings, wh
CVE-2022-1780 is a medium-severity flaw (CVSS 5.4) affecting latex. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 5.4 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | Required |
| EPSS exploit chance | 0.3% (top 77%) |
| CISA exploited list | No |
| Weakness | CWE-352 |
| Published | 2022-06-13 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2022-1780?
latex: upgrade to newer than 3.4.10. Exact commands for each OS are on this page.
Is CVE-2022-1780 being exploited?
CVE-2022-1780 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2022-1780 affect?
CVE-2022-1780 affects latex. Severity is medium (CVSS 5.4). 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 Scrip
How urgent is CVE-2022-1780?
Priority 30/100. Public exploit reference