CVE-2023-51531: WordPress Thrive Automator Plugin <= 1.17 is vulnerable to Cross Site Request Forgery (CSRF)
Published Feb 29, 2024
·Updated
Cross-Site Request Forgery (CSRF) vulnerability in Thrive Themes Thrive Automator.This issue affects Thrive Automator: from n/a through 1.17.
Affected Software
3 affected components
Thrive Themes Thrive Automator<=1.17
WordPress Thrive Automator Plugin<=1.17
Thrivethemes Thrive Automator Wordpress<1.17.1
Remediation
Information
Update to 1.17.1 or a higher version.
Event History
Feb 29, 2024
CVE Published
via MITRE·04:59 AM
Data Sourced
via MITRE·04:59 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·05:15 AM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2023-51531?
CVE-2023-51531 is classified as a moderate severity Cross-Site Request Forgery (CSRF) vulnerability.
2
How do I fix CVE-2023-51531?
To mitigate CVE-2023-51531, update Thrive Automator to the latest version above 1.17.
3
Which versions are affected by CVE-2023-51531?
CVE-2023-51531 affects Thrive Automator versions from n/a through 1.17.
4
Is CVE-2023-51531 specific to any particular software?
Yes, CVE-2023-51531 specifically affects Thrive Themes Thrive Automator and the WordPress Thrive Automator Plugin.
5
What type of vulnerability is CVE-2023-51531?
CVE-2023-51531 is a Cross-Site Request Forgery (CSRF) vulnerability.