# CVE-2026-103694: Mobile builder <= 1.4.2 - Subscriber+ Privilege Escalation to Admin

> A logged-in subscriber can escalate privileges to administrator by exploiting improper user meta key restrictions in the Mobile builder plugin.

- **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:** 11 Oct 2026
- **Updated:** 11 Oct 2026
- **Also known as:** GHSA-jm9q-87xx-cg6m

## What is CVE-2026-103694?

CVE-2026-103694 is a high-severity vulnerability in Unknown Mobile builder, published on 11 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Mobile builder WordPress plugin through 1.4.2 does not properly restrict which user meta keys a logged-in user can update through one of its REST routes, allowing any user with a self-registered account, such as a customer, to grant themselves the administrator role.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-103694 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103694 is a high-severity vulnerability in Unknown Mobile builder, published on 11 Oct 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-103694 in the wild and no public exploit code.

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

## Sources

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

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