# CVE-2026-81583: Theme My Login 7.0 - 7.1.15 - Subscriber+ Unauthorised Multisite Site Creation and Privilege Escalation

> Attackers can create unauthorized sites and gain administrator privileges on multisite WordPress installations using the Theme My Login plugin.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-rx7v-j56c-vf8f

## What is CVE-2026-81583?

CVE-2026-81583 is a medium-severity vulnerability in Unknown Theme My Login, published on 2 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-81583?


## How do I fix CVE-2026-81583?

No fix has been published for CVE-2026-81583 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-81583 being exploited?

There is no known exploitation of CVE-2026-81583 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-81583 and fix it if it is affected.

What it is: CVE-2026-81583 is a medium-severity vulnerability in Unknown Theme My Login, published on 2 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-81583 in the wild and no public exploit code.

Affected product: Unknown Theme My Login. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-81583/ (Markdown: https://insights.sbomify.com/CVE-2026-81583/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-81583
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-81583
- OSV: https://osv.dev/vulnerability/CVE-2026-81583

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-81583/
Summaries are generated and may contain mistakes; the official description above is the record.