# CVE-2026-15368: Profile Builder < 3.16.4 - Unauthenticated Account Takeover via Auto-Login After Registration

> Unauthenticated attackers can hijack sessions of arbitrary users, including administrators, via flawed auto-login logic in the User Profile Builder plugin.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2026
- **Updated:** 5 Aug 2026
- **Also known as:** GHSA-p782-jwj4-rqqc

## What is CVE-2026-15368?

CVE-2026-15368 is a high-severity authentication bypass vulnerability in Unknown User Profile Builder, published on 1 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The User Profile Builder  WordPress plugin before 3.16.4 does not correctly bind the automatic login performed after user registration to the newly created account, allowing unauthenticated attackers to obtain an authenticated session for an arbitrary existing user, including administrators, on sites using a supported but non-default configuration.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-15368 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15368 is a high-severity authentication bypass vulnerability in Unknown User Profile Builder, published on 1 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-15368 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-15368/ (Markdown: https://insights.sbomify.com/CVE-2026-15368/index.md)
```

## Sources

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

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