Skip to main content

Theme My Login CVE-2026-81583

| EUVDEUVD-2026-69857 MEDIUM
Improper Privilege Management (CWE-269)
2026-09-02 WPScan GHSA-rx7v-j56c-vf8f
5.4
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify target WordPress multisite with Theme My Login installed
  2. Delivery
    Obtain or use existing subscriber account (or exploit on open-registration networks unauthenticated)
  3. Exploit
    Submit site-signup request bypassing network registration policy
  4. Execution
    Receive administrator grant on newly created site
  5. Persist
    Install malicious plugin via site admin panel
  6. Impact
    Achieve remote code execution on server

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires WordPress to be running in multisite mode with the Theme My Login plugin (versions before 7.2.0) active on the network. For the primary attack path, the attacker must hold a subscriber-level account on the multisite network (PR:L per CVSS). On some networks where registration is open, the description explicitly notes that unauthenticated users may also be able to exploit this, making the authentication requirement network-configuration-dependent. Limits to exploitation: single-site WordPress installations are not affected; the attacker does not gain network-admin (superadmin) rights, only site-admin rights over the newly created site; and exploitation is limited to networks where the Theme My Login plugin is installed and active.

Impact

The vendor-provided CVSS 3.1 score of 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L) understates real-world impact: gaining site administrator over a WordPress site confers the ability to install arbitrary plugins, modify themes, and access all data within that site, which is better characterized as I:H rather than I:L. A:L in the provided vector is unexplained by the description and appears inflated - no availability mechanism is apparent. Scope is unchanged (S:U) at the network level since the attacker does not gain superadmin/network-admin rights, but within the new site, the compromise is effectively total. The publicly available PoC (WPScan) significantly lowers the exploitation bar. EPSS data is not present in the input, so probability of mass exploitation is unknown; however, the ease of exploitation (AC:L, PR:L) and existing PoC together suggest meaningful real-world risk for any multisite network running the unpatched plugin. No CISA KEV listing is indicated, so exploitation is not confirmed as active at time of analysis.

Exploit ScenarioDerived

An attacker with a subscriber account on a WordPress multisite network (e.g., a free-tier user who registered before registration was disabled by the network admin) calls the Theme My Login multisite site-signup endpoint with a chosen subdomain. The plugin processes the signup without checking the network's registration policy, creates the site, and grants the attacker administrator access to it. From that admin panel the attacker can install plugins with arbitrary PHP code, escalating to full RCE on the hosting server if file-system permissions allow. A public PoC is available via WPScan, making this accessible to non-expert attackers.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 02, 2026

Privilege escalation in the Theme My Login WordPress plugin (versions before 7.2.0) allows low-privileged users to silently bypass the network's site-creation restrictions on multisite WordPress installations, gaining administrator-level control over a newly created site. Subscriber-level authenticated users - and on some networks, unauthenticated users - can invoke the site-signup flow to create sites even when the network's registration setting prohibits it. A publicly available proof-of-concept exploit exists, raising the urgency for patching. The vendor has released a fix in version 7.2.0.

RemediationAI

Update Theme My Login to version 7.2.0 or later, which enforces the network registration setting during multisite site signups. The patch is confirmed available from the vendor. Until patching is possible, network administrators can mitigate by temporarily deactivating the Theme My Login plugin on the multisite network and reverting to default WordPress login pages - this removes the vulnerable signup flow at the cost of losing the plugin's UI customizations. Alternatively, network admins can disable site registration entirely at the WordPress network level (Settings → Network Settings → Allow new registrations → 'No registrations allowed'), which is a safe compensating control with no functional side effects for networks that do not legitimately require new site creation. References: https://wpscan.com/vulnerability/6ced93ee-5629-42a4-9103-44cf99265bd2/

Affected VersionsENISA

Theme My Login 7.0 <7.2.0

Affected Packages

euvd theme_my_login fix: 7.2.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Theme My Login is a WordPress plugin that customizes the default WordPress login, registration, and lost-password pages, and extends those flows for WordPress multisite installations. In multisite mode, WordPress networks expose a site-signup flow that is supposed to be gated by the network's registration option (e.g., 'none', 'user', 'blog', 'all'). The plugin's handling of multisite site signups fails to check this option (CWE-269: Improper Privilege Management), effectively ignoring the administrator-configured gating. The affected CPE is cpe:2.3:a:unknown:theme_my_login:*:*:*:*:*:*:*:* covering all versions before 7.2.0. Because WordPress multisite is the deployment context, only sites running the plugin in a multisite network are vulnerable.

Know when Theme My Login gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 5.4 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
vuln.today AI 8.5 HIGH

Scope change applies as subscriber crosses privilege boundary to site-admin; integrity is H (full site control), not L; A:L in provided vector is unsupported by description.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:L/SI:H/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

Lifecycle Timeline

4
CVSS changed
Sep 02, 2026 - 11:22 NVD
5.4 (MEDIUM)
Patch available
Sep 02, 2026 - 07:01 EUVD
CVE Published
Sep 02, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 02, 2026 - 06:00 cve.org
MEDIUM 5.4

DescriptionCVE.org

The My Login WordPress plugin before 7.2.0 does not enforce the network's registration setting when processing site signups on multisite installations, allowing users with a subscriber account, and unauthenticated users on some networks, to create new sites and be granted administrator over them.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
Medium
popular WordPress login-customization plugin, multisite deployments only
Exploit
POC
Public exploit code exists
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

47
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +27
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy