Theme My Login vulnerabilities
3 known CVE vulnerabilities in Theme My Login, translated and rated.
- CVE-2026-89079Critical
The Theme My Login plugin for WordPress is vulnerable to privilege escalation via account takeover in versions up to, and including, 7.2.1. This is due to the plugin not properly validating a user's identity prior to updating their password, allowing unauthenticated attackers to change arbitrary user's passwords on multi-site setups in certain configurations.
- CVE-2026-83628Medium
The Theme My Login plugin for WordPress is vulnerable to Missing Authorization in versions up to and including 7.1.15 on Multisite installations. This is due to the `tml_ms_signup_handler()` function's `gimmeanotherblog` branch failing to enforce the network's `active_signup` registration policy, checking only `is_user_logged_in()` while sibling branches such as `validate-blog-signup` apply the full policy gate. This allows authenticated attackers with Subscriber-level access and above to directly POST `stage=gimmeanotherblog` to Theme My Login's signup route, bypassing the configured registration policy entirely — even when it is set to `none` or `user` — which causes `wpmu_create_blog()` to execute with the attacker's user ID, after which WordPress core assigns the Administrator role on the newly created subsite. The privilege gain is scoped to the newly created subsite only; the attacker's account retains Subscriber-level access on the main site and does not obtain Super Admin or network-level capabilities.
- CVE-2026-66681Medium
CSRF vulnerability in Theme My Login versions up to 7.1.14 allows an unauthenticated attacker to perform unauthorized actions.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS

