Secuno
ENNL
Book demo

CVE-2026-16038

MStore API WordPress plugin broken access control

9.1 CRITICALEPSS 0.42%
  1. Published7 Aug 2026

Description

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

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-891089.1
SAP Manufacturing Integration and Intelligence does not sufficiently enforce…
CVE-2026-1096408.1
Frappe ERPNext before 16.22.0 contains a missing authorization vulnerability that…
CVE-2026-843158.3
Nginx UI is a web user interface for the Nginx web server. Prior to 2.4.1, Nginx UI…
CVE-2026-571189.8
PraisonAI is a multi-agent teams system. Prior to praisonaiagents 1.6.59,…
CVE-2026-1092018.3
LogicalDOC Community Edition through 9.3 contains a missing authorization vulnerability…
CVE-2026-1091858.8
jshERP through 3.6 contains a missing authorization vulnerability in the UserController…

Frequently asked

Is CVE-2026-16038 being actively exploited?

CVE-2026-16038 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.42%.

How severe is CVE-2026-16038?

CVE-2026-16038 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.42% probability of exploitation.

How do I fix CVE-2026-16038?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-16038 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.