# CVE-2019-25344: MobileGo 8.5.0 - Insecure File Permissions

> Local attackers can modify application executables to gain administrative privileges and create new admin accounts.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-q7w4-8rgm-gmv2

## What is CVE-2019-25344?

CVE-2019-25344 is a high-severity vulnerability in Wondershare MobileGo, published on 12 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Wondershare MobileGo 8.5.0 contains an insecure file permissions vulnerability that allows local users to modify executable files in the application directory. Attackers can replace the original MobileGo.exe with a malicious executable to create a new user account and add it to the Administrators group with full system access.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2019-25344?

It affects 1 product.


Products: Wondershare Mobilego.

## How do I fix CVE-2019-25344?

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

## Is CVE-2019-25344 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25344 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25344 and fix it if it is affected.

What it is: CVE-2019-25344 is a high-severity vulnerability in Wondershare MobileGo, published on 12 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25344 exists.

Affected product: Wondershare MobileGo. 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-2019-25344/ (Markdown: https://insights.sbomify.com/CVE-2019-25344/index.md)
```

## Sources

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

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