# CVE-2026-15451: Privilege escalation in MemberPress Corporate Accounts

> Authenticated subscribers with corporate accounts can escalate privileges to administrator via mass assignment in sub-account creation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 12 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-43m3-49cj-3hqf

## What is CVE-2026-15451?

CVE-2026-15451 is a high-severity vulnerability in MemberPress Corporate Accounts, published on 12 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The MemberPress Corporate Accounts plugin for WordPress is vulnerable to Privilege Escalation in versions up to, and including, 1.5.39. This is due to a mass assignment vulnerability in the 'add_sub_account_user' function that passes the raw 'userdata' array to 'wp_insert_user' without filtering dangerous keys like role or ID. This makes it possible for authenticated attackers, with subscriber-level access and above who hold a corporate account, to create new administrator accounts or hijack existing administrator accounts by overwriting their email addresses. The vulnerability was partially patched in version 1.5.39.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-15451 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15451 is a high-severity vulnerability in MemberPress Corporate Accounts, published on 12 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-15451 in the wild and no public exploit code.

Affected product: MemberPress Corporate Accounts. 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-15451/ (Markdown: https://insights.sbomify.com/CVE-2026-15451/index.md)
```

## Sources

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

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