# CVE-2026-111982: Profile Builder < 4.0.5 - Multisite Subsite Admin+ Network Super Admin Account Takeover via Edit Profile Email Change


- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-qgfq-45qj-365w

## What is CVE-2026-111982?

CVE-2026-111982 is a high-severity vulnerability in Unknown User Profile Builder, published on 23 Oct 2026. 

### Official description

The User Profile Builder  WordPress plugin before 4.0.5 does not verify that a user is authorized to edit the specific account selected on its front-end Edit Profile form, allowing an Administrator of a Multisite subsite to change any other user's account email, including a Network Super Admin's, and take over that account through the password-reset flow.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-111982 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111982 is a high-severity vulnerability in Unknown User Profile Builder, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-111982 in the wild and no public exploit code.

Affected product: Unknown User Profile Builder. 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-111982/ (Markdown: https://insights.sbomify.com/CVE-2026-111982/index.md)
```

## Sources

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

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