Authentication Bypass in Wordpress Plugin Mobile App Native (CVE-2017-6104)
Summary
Authentication bypass in Wordpress Plugin Mobile App Native (CVE-2017-6104). Data can be tampered with by attackers.
Original description
The description as published by the source.
Remote file upload vulnerability in Wordpress Plugin Mobile App Native 3.0.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A weakness called CVE-2017-6104 was discovered in Wordpress Plugin Mobile App Native.
In plain terms, it is an authentication weakness that allows impersonation.
Severity is High (CVSS 7.5/10). If exploited, attackers can leak data or disrupt key functionality.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "Wordpress Plugin Mobile App Native CVE-2017-6104".
CVE-2017-6104 (Wordpress Plugin Mobile App Native). Severity: High / CVSSv3 7.5. Category: CWE-287.
Response plan:
- Check the vendor advisory for affected versions and the patched release.
- If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
- If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
- Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
A weakness (CVE-2017-6104) in Wordpress Plugin Mobile App Native. In plain words, it is an authentication weakness that allows impersonation.
Target versions of Wordpress Plugin Mobile App Native (see vendor advisory). If running in production, identify exposure immediately.
Severity: High (CVSS 7.5/10). If exploited, attackers can leak data or disrupt key functionality.
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-287)
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
References
- advisory securityfocus.com
- exploit vapidlabs.com
- exploit wpvulndb.com
- exploit exploit-db.com