# CVE-2026-14237: Vitepos < 3.6.0 - Outlet Manager+ Privilege Escalation

> An Outlet Manager can reset any user's password, including administrators, due to missing authorization checks in the password-reset API.

- **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
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-x2ww-v6rp-cf3p

## What is CVE-2026-14237?

CVE-2026-14237 is a high-severity vulnerability in Unknown Vitepos, published on 10 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The vitepos WordPress plugin before 3.6.0, Vitepos  WordPress plugin before 3.5.0 do not perform a per-target authorization check in their point-of-sale password-reset API and grant the custom Outlet Manager role an over-broad password-reset capability by default, allowing an Outlet Manager to reset any user's password, including an administrator's, and take over the account.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-14237 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14237 is a high-severity vulnerability in Unknown Vitepos, published on 10 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14237 in the wild and no public exploit code.

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

## Sources

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

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