CVE-2024-37118: WordPress Uncanny Automator Pro plugin <= 5.3 - Cross Site Request Forgery (CSRF) Leading to License Settings Reset vulnerability
Published Jun 21, 2024
·Updated
Cross Site Request Forgery (CSRF) vulnerability in Uncanny Owl Uncanny Automator Pro.This issue affects Uncanny Automator Pro: from n/a through 5.3.
Affected Software
1 affected component
Uncannyowl Uncanny Automator Wordpress<=5.3
Event History
Jun 21, 2024
CVE Published
via MITRE·01:47 PM
Data Sourced
via MITRE·01:47 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:15 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2024-37118?
CVE-2024-37118 is classified as a moderate severity Cross Site Request Forgery (CSRF) vulnerability.
2
How do I fix CVE-2024-37118?
To fix CVE-2024-37118, update Uncanny Automator Pro to the latest version beyond 5.3.
3
What versions of Uncanny Automator Pro are affected by CVE-2024-37118?
CVE-2024-37118 affects all versions of Uncanny Automator Pro from n/a through 5.3.
4
What types of attacks can be executed through CVE-2024-37118?
CVE-2024-37118 allows attackers to potentially reset license settings due to CSRF exploits.
5
Is user authentication sufficient to mitigate CVE-2024-37118?
User authentication alone is not sufficient to mitigate CVE-2024-37118, and developers should implement CSRF tokens.