CVE-2023-2732 in the critical feed json
MStore API <= 3.9.2 - Authentication Bypass
published 2023-05-25 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-34193
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 67.3%
- EPSS 67.3% chance of exploitation in 30 days, percentile 99.3%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
The MStore API plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 3.9.2. This is due to insufficient verification on the user being supplied during the add listing REST API request through the plugin. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the user id.
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 21 mo ago
Exploit prediction
67.28% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template MStore API <= 3.9.2 - Authentication Bypass nuclei detection template
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
-
- CWE-288 Authentication Bypass Using an Alternate Path or Channel
- Technology feeds
References
-
plugins.trac.wordpress.org
/browser/mstore-api/tags/3.9.0/controllers/listing-rest-api/class.api.fields.php#L1079
patch
-
plugins.trac.wordpress.org
/changeset?sfp_email=&sfph_mail=&reponame=&new=2916124%40mstore-api&old=2915729%40mstore-api&sfp_email=&sfph_m
patch
-
wordfence.com
/threat-intel/vulnerabilities/id/f00761a7-fe24-49a3-b3e3-a471e05815c1?source=cve
third-party-advisory
Sources
- CVE List CVE-2023-2732
- NVD CVE-2023-2732
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.