Lucene search
+L

352 matches found

Nuclei
Nuclei
added 16 hours ago43 views

MStore API <= 3.9.1 - Authentication Bypass

The MStore API plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 3.9.1. This is due to insufficient verification on the user being supplied during the cart sync from mobile REST API request through the plugin. This makes it possible for unauthenticated...

9.8CVSS8.6AI score0.03805EPSS
SaveExploits0References3
Nuclei
Nuclei
added 16 hours ago17 views

MStore API <= 4.10.7 - Unauthorized Account Access and Privilege Escalation

The MStore API plugin for WordPress is vulnerable to Unauthorized Account Access and Privilege Escalation in versions up to, and including, 4.10.7 due to improper implementation of the Apple login feature. This allows unauthenticated attackers to log in as any user as long as they know the user's...

9.8CVSS8.5AI score0.02888EPSS
SaveExploits0References4
Nuclei
Nuclei
added 16 hours ago74 views

MStore API < 3.9.8 - SQL Injection

The MStore API WordPress plugin before 3.9.8 is vulnerable to Blind SQL injection via the productid parameter. id: CVE-2023-3077 info: name: MStore API 3.9.8 - SQL Injection author: DhiyaneshDK severity: critical description: | The MStore API WordPress plugin before 3.9.8 is vulnerable to Blind S...

9.8CVSS8.8AI score0.05505EPSS
SaveExploits2References2
Nuclei
Nuclei
added 3 days ago127 views

MStore API <= 3.9.2 - Authentication Bypass

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 ...

9.8CVSS8.5AI score0.67511EPSS
SaveExploits3References5
NVD
NVD
added 4 days ago9 views

CVE-2026-16039

The MStore API WordPress plugin before 4.21.0 does not restrict its vendor-orders endpoint to the caller's own orders, allowing any authenticated user, including Subscribers, to read every WooCommerce order in the store together with each customer's personal information...

6.5CVSS0.00201EPSS
SaveExploits0References1
NVD
NVD
added 4 days ago8 views

CVE-2026-16041

The MStore API WordPress plugin before 4.21.0 does not perform authorization or purchase-ownership checks on its REST product-review creation route, allowing an unauthenticated attacker to create WooCommerce product reviews with an attacker-chosen reviewer name, email and star rating on stores...

7.5CVSS0.00208EPSS
SaveExploits0References1
NVD
NVD
added 4 days ago10 views

CVE-2026-16030

The MStore API WordPress plugin before 4.21.0 does not correctly verify the cryptographic signature of the token used to authenticate its phone-based login, allowing unauthenticated attackers who know a registered user's phone number to forge a token and take over that user's account, including...

8.1CVSS0.00226EPSS
SaveExploits0References1
NVD
NVD
added 4 days ago8 views

CVE-2026-16038

The MStore API WordPress plugin before 4.21.0 does not verify the payment with the payment gateway before marking an order as paid on several of its payment-completion endpoints, allowing an unauthenticated attacker to mark an arbitrary order fully paid without paying and obtain goods or services...

9.1CVSS0.0024EPSS
SaveExploits0References1
CVE
CVE
added 4 days ago39 views

CVE-2026-16041

The CVE-2026-16041 entry concerns the MStore API WordPress plugin prior to version 4.21.0. The REST endpoint used for creating product reviews lacks authorization and purchase-ownership checks, allowing an unauthenticated attacker to submit WooCommerce product reviews with arbitrary reviewer name...

7.5CVSS5.5AI score0.00208EPSS
SaveExploits0References1
EUVD
EUVD
added 4 days ago13 views

EUVD-2026-54386

The MStore API WordPress plugin before 4.21.0 does not verify the payment with the payment gateway before marking an order as paid on several of its payment-completion endpoints, allowing an unauthenticated attacker to mark an arbitrary order fully paid without paying and obtain goods or services...

9.1CVSS5.6AI score0.0024EPSS
SaveExploits0References1
EUVD
EUVD
added 4 days ago10 views

EUVD-2026-54385

The MStore API WordPress plugin before 4.21.0 does not correctly verify the cryptographic signature of the token used to authenticate its phone-based login, allowing unauthenticated attackers who know a registered user's phone number to forge a token and take over that user's account, including...

8.1CVSS5.5AI score0.00226EPSS
SaveExploits0References1
EUVD
EUVD
added 4 days ago13 views

EUVD-2026-54387

The MStore API WordPress plugin before 4.21.0 does not restrict its vendor-orders endpoint to the caller's own orders, allowing any authenticated user, including Subscribers, to read every WooCommerce order in the store together with each customer's personal information...

6.5CVSS5.5AI score0.00201EPSS
SaveExploits0References1
Cvelist
Cvelist
added 4 days ago32 views

CVE-2026-16030 MStore API < 4.21.0 - Unauthenticated Account Takeover via Firebase Phone Authentication

The MStore API WordPress plugin before 4.21.0 does not correctly verify the cryptographic signature of the token used to authenticate its phone-based login, allowing unauthenticated attackers who know a registered user's phone number to forge a token and take over that user's account, including...

0.00226EPSS
SaveExploits0References1
Cvelist
Cvelist
added 4 days ago34 views

CVE-2026-16038 MStore API < 4.21.0 - Unauthenticated Payment Bypass via Multiple Payment Gateways

The MStore API WordPress plugin before 4.21.0 does not verify the payment with the payment gateway before marking an order as paid on several of its payment-completion endpoints, allowing an unauthenticated attacker to mark an arbitrary order fully paid without paying and obtain goods or services...

0.0024EPSS
SaveExploits0References1
Cvelist
Cvelist
added 4 days ago33 views

CVE-2026-16039 MStore API < 4.21.0 - Subscriber+ Order and Customer PII Disclosure via IDOR

The MStore API WordPress plugin before 4.21.0 does not restrict its vendor-orders endpoint to the caller's own orders, allowing any authenticated user, including Subscribers, to read every WooCommerce order in the store together with each customer's personal information...

0.00201EPSS
SaveExploits0References1
EUVD
EUVD
added 4 days ago10 views

EUVD-2026-54388

The MStore API WordPress plugin before 4.21.0 does not perform authorization or purchase-ownership checks on its REST product-review creation route, allowing an unauthenticated attacker to create WooCommerce product reviews with an attacker-chosen reviewer name, email and star rating on stores...

7.5CVSS5.5AI score0.00208EPSS
SaveExploits0References1
Cvelist
Cvelist
added 4 days ago34 views

CVE-2026-16041 MStore API < 4.21.0 - Unauthenticated Product Review Creation

The MStore API WordPress plugin before 4.21.0 does not perform authorization or purchase-ownership checks on its REST product-review creation route, allowing an unauthenticated attacker to create WooCommerce product reviews with an attacker-chosen reviewer name, email and star rating on stores...

0.00208EPSS
SaveExploits0References1
CVE
CVE
added 4 days ago36 views

CVE-2026-16039

CVE-2026-16039 affects the MStore API WordPress plugin prior to 4.21.0. The vendor-orders endpoint does not restrict access to the caller’s orders, allowing any authenticated user (including Subscribers) to read every WooCommerce order and associated customer personal information. Root cause: imp...

6.5CVSS5.5AI score0.00201EPSS
SaveExploits0References1
CVE
CVE
added 4 days ago47 views

CVE-2026-16038

Summary : CVE-2026-16038 affects the MStore API WordPress plugin prior to 4.21.0. The vulnerability arises because the plugin does not verify payment with the gateway on several payment-completion endpoints, allowing an unauthenticated attacker to mark an arbitrary order as fully paid and obtain ...

9.1CVSS5.6AI score0.0024EPSS
SaveExploits0References1
CVE
CVE
added 4 days ago54 views

CVE-2026-16030

CVE-2026-16030 affects the MStore API WordPress plugin prior to 4.21.0. The root cause is improper verification of the cryptographic signature on the token used for phone-based login, enabling unauthenticated attackers who know a registered user’s phone number to forge a token and take over that ...

8.1CVSS5.5AI score0.00226EPSS
SaveExploits0References1
Rows per page
Query Builder