CVE-2024-7422

Theme My Login <= 7.1.7 - Cross-Site Request Forgery to Settings Update

2024-08-15 00:00
vgo0

Strategic Overview

Status
Patched in 7.1.8
Affected Plugin
Theme My Login
Affected Version
<= 7.1.7
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-7422
View all Theme My Login vulnerabilities

At a glance

CVE-2024-7422 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Theme My Login WordPress plugin, affecting versions <= 7.1.7. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 7.1.8; sites on affected versions should update now. Disclosed August 2024, reported by vgo0.

Vulnerability Overview

The Theme My Login plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 7.1.7. This is due to missing or incorrect nonce validation on the tml_admin_save_ms_settings() function. This makes it possible for unauthenticated attackers to update the theme's settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. Please note that this only affects multi-site instances.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Theme My Login <= 7.1.7 carries this weakness at tml_admin_save_ms_settings(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Theme My Login the fix is 7.1.8: builds <= 7.1.7 are affected, anything from 7.1.8 onward is not.

Remediation

Update to version 7.1.8, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Theme My Login: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Theme My Login 7.1.8 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-7422https://www.wordfence.com/threat-intel/vulnerabilities/id/0fb8e956-3a95-4e55-9816-be7eddb5835dhttps://nvd.nist.gov/vuln/detail/CVE-2024-7422

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C