CVE-2020-36713 json
MStore API <= 2.1.5 - Authentication Bypass
published 2023-06-07 3 y ago modified 2026-06-17 4 mo ago also EUVD-2020-24155
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
The MStore API plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 2.1.5. This is due to unrestricted access to the 'register' and 'update_user_profile' routes. This makes it possible for unauthenticated attackers to create new administrator accounts, delete existing administrator accounts, or escalate privileges on any account.
Patch / fix
- inspireui MStore API – Create Native Android & iOS Apps On The Cloud 2.1.6
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 22 mo ago
Exploit prediction
1.60% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- blog.nintechnet.com https://blog.nintechnet.com/critical-vulnerability-fixed-in-wordpress-mstore-api-plugin/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- inspireui MStore API – Create Native Android & iOS Apps On The Cloud
Classification
- Weakness
- Technology feeds
References
-
blog.nintechnet.com
/critical-vulnerability-fixed-in-wordpress-mstore-api-plugin/
exploit
-
wordfence.com
/threat-intel/vulnerabilities/id/934c3ce9-cf2d-4bf6-9a34-f448cb2e5a1d?source=cve
third-party-advisory
-
acunetix.com
/vulnerabilities/web/wordpress-plugin-mstore-api-security-bypass-2-1-5/
third-party-advisory
Sources
- CVE List CVE-2020-36713
- NVD CVE-2020-36713
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.