CVE-2026-83628
Last modified
CVE-2026-83628 is a medium-severity vulnerability rated 4.3/10 on the CVSS scale. 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. EPSS estimates a 0.24% chance of exploitation in the next 30 days.
Description
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 makes it possible for 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 via `add_user_to_blog()`. 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 such as `manage_network` or `manage_sites`.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| jfarthing84 | Theme My Login | <= 7.1.15 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-83628?
How severe is CVE-2026-83628?
How do I fix CVE-2026-83628?
How Strix Helps
- Uncovering a hidden BOLA in Appsmith's snapshot logicStrix autonomously discovered a BOLA/IDOR vulnerability in Appsmith's snapshot deletion path.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-83618xmldom is a pure JavaScript W3C standard-based (XML DOM Leve…8.7
- CVE-2026-83619xmldom is a pure JavaScript W3C standard-based (XML DOM Leve…8.7
- CVE-2026-8362A stack-based buffer overflow condition exists in WOSDefault…9.8
- CVE-2026-83621ntopng is a web-based network traffic monitoring application…8.1
- CVE-2026-83625The Contact Form by Supsystic plugin for WordPress is vulner…7.2
- CVE-2026-83627The Hummingbird – Speed Optimization, Caching, Minify, Compr…9.8
- CVE-2026-8363A stack-based buffer overflow condition exists in WOSDeviceD…9.8
- CVE-2026-8364Gladinet Triofox Cloud Server Agent Access Service (GladServ…9.8
- CVE-2026-8365The Blocksy theme for WordPress is vulnerable to PHP Object …8.8
- CVE-2026-83660Adobe Campaign Classic (ACC) is affected by a Server-Side Re…9.9
- CVE-2026-8367aria2c accepts a server certificate with incorrect Extended …5.3
- CVE-2026-8368LWP::UserAgent versions before 6.83 for Perl leak Authorizat…6.5
Are you affected by CVE-2026-83628?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
