# CVE-2025-11127: Mstoreapp Mobile (App <= 2.08, Multivendor <= 9.0.1) - Unauthenticated Privilege Escalation

> Unauthenticated attackers can hijack user sessions by knowing email addresses, leading to account takeover in Mstoreapp Mobile plugins.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/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:** 21 Nov 2025
- **Updated:** 21 Nov 2025
- **Also known as:** GHSA-9mf8-fwp6-wv6x

## What is CVE-2025-11127?

CVE-2025-11127 is a critical authentication bypass vulnerability in Unknown Mstoreapp Mobile App, published on 21 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Mstoreapp Mobile App WordPress plugin through 2.08 and Mstoreapp Mobile Multivendor through 9.0.1 do not properly verify users identify when using an AJAX action, allowing unauthenticated users to retrieve a valid session for arbitrary users by knowing their email address.

## Which versions are affected by CVE-2025-11127?


## How do I fix CVE-2025-11127?

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

## Is CVE-2025-11127 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11127 and fix it if it is affected.

What it is: CVE-2025-11127 is a critical authentication bypass vulnerability in Unknown Mstoreapp Mobile App, published on 21 Nov 2025. 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-2025-11127 in the wild and no public exploit code.

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

## Sources

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

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