CVE-2026-83628 jfarthing84 CVE debrief

Who should care

Defenders responsible for WordPress Multisite installations using Theme My Login plugin version 7.1.15 or earlier should assess exposure and prioritize verification and remediation.

Why it matters

Defenders should prioritize verifying Multisite installations using Theme My Login plugin version 7.1.15 or earlier and assess exposure to authenticated attackers. The vulnerability allows authenticated attackers with Subscriber-level access and above to bypass the configured registration policy and create a new subsite with Administrator role.

• Privilege escalation to Administrator role on newly created subsites
• Bypassing of configured registration policy
• Potential for unauthorized site creation

Technical summary

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.

Defensive priority

Defenders should prioritize verifying Multisite installations using Theme My Login plugin version 7.1.15 or earlier and assess exposure to authenticated attackers.

Recommended defensive actions

• Verify Multisite installations using Theme My Login plugin version 7.1.15 or earlier
• Assess exposure to authenticated attackers with Subscriber-level access and above
• Update Theme My Login plugin to a version that fixes the vulnerability
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is due to the `tml_ms_signup_handler()` function's `gimmeanotherblog` branch failing to enforce the network's `active_signup` registration policy. This issue allows attackers to directly POST `stage=gimmeanotherblog` to Theme My Login's signup route, bypassing the configured registration policy.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.