Raw vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2019-25344 is a high-severity Incorrect Permission Assignment for Critical Resource (CWE-732) vulnerability in Wondershare Mobilego. Its CVSS base score is 8.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Services File Permissions Weakness (T1574.010); ranked at the 6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-6 (Least Privilege) and CM-6 (Configuration Settings) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2019-25344 is an insecure file permissions vulnerability (CWE-732) in Wondershare MobileGo version 8.5.0. The flaw enables local users to modify executable files in the application's installation directory due to inadequate permissions on these files.
A local attacker with low privileges can exploit this vulnerability by replacing the legitimate MobileGo.exe with a malicious executable. When the application is launched by an administrator or under elevated context, the substituted binary executes with sufficient rights to create a new user account and add it to the Administrators group, achieving full system access. The issue carries a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), reflecting high impacts on confidentiality, integrity, and availability.
Advisories and resources, including a proof-of-concept exploit at https://www.exploit-db.com/exploits/47667 and a VulnCheck advisory at https://www.vulncheck.com/advisories/mobilego-insecure-file-permissions, detail the vulnerability. Vendor pages at https://www.wondershare.net/ and https://www.wondershare.net/mobilego/ provide additional context on the software.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2019-19482
Vulnerability Data
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…
more
to the Administrators group with full system access.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Insecure executable permissions (CWE-732) directly enable binary replacement for local privilege escalation to SYSTEM/admin.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires processes to protect application executables like MobileGo.exe from unauthorized modification by local users.
Mandates restrictive configuration settings on application directories and files to prevent low-privileged local users from modifying executables.
Enforces least privilege to ensure low-privileged local users lack write access to the application's installation directory and executables.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
By requiring owners to determine and document the exact permissions needed for each asset, the control reduces the likelihood that default or overly permissive file and resource permissions will be left in place.
Documented provisioning and revocation procedures reduce the chance that critical resources retain overly permissive default or leftover permissions after personnel changes.
Documented authorization, expiry rules, and audit logging of privileged accounts make it harder for critical resources to retain overly permissive or stale permission assignments.
Requiring explicit configuration of access controls and permissions for files, applications and services counters the assignment of overly permissive default or incorrect file-system rights.
Enforcing differentiated permissions on the source-code repository and program listings stops the assignment of overly broad default or inherited permissions to critical resources.
By defining and enforcing secure permission settings in configuration templates, the control reduces the likelihood that critical resources receive incorrect permission assignments.