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

Published Jun 13, 2022
·
Updated

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

Affected Software

1 affected component
Latex Project Latex Wordpress<=3.4.10

Event History

Jun 13, 2022
CVE Published
via MITRE·12:42 PM
Data Sourced
via MITRE·12:42 PM
DescriptionWeakness

Frequently Asked Questions

1

What is the severity of CVE-2022-1780?

CVE-2022-1780 is classified as a high severity vulnerability due to the potential for CSRF attacks leading to stored cross-site scripting.

2

How do I fix CVE-2022-1780?

To fix CVE-2022-1780, update the LaTeX for WordPress plugin to version 3.4.10 or later.

3

What does CVE-2022-1780 exploit in the LaTeX for WordPress plugin?

CVE-2022-1780 exploits the lack of CSRF checks when updating settings, allowing unauthorized changes by attackers.

4

Can CVE-2022-1780 lead to data exposure?

Yes, CVE-2022-1780 could lead to data exposure through stored cross-site scripting if exploited.

5

Who is affected by CVE-2022-1780?

Users of the LaTeX for WordPress plugin versions up to and including 3.4.10 are affected by CVE-2022-1780.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203