PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-16039 MStore API CVE debrief

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. This vulnerability affects WooCommerce site owners and administrators, as they need to verify and restrict access to the vendor-orders endpoint to prevent unauthorized access to sensitive order information. The vulnerability has a CVSS score of 6.5 and a severity of MEDIUM. Evidence is limited; defenders should verify affected versions, review access controls, and monitor for unauthorized access attempts. The CVE record was published on 2026-08-07T06:16:56.060Z and has not been modified since then.

Vendor
MStore API
Product
MStore API WordPress plugin
CVSS
MEDIUM 6.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-07
Original CVE updated
2026-08-26
Advisory published
2026-08-07
Advisory updated
2026-08-26

Who should care

WooCommerce site owners and administrators, WordPress security teams, users of the MStore API plugin, and security teams responsible for vulnerability management and remediation efforts.

Technical summary

The MStore API WordPress plugin before 4.21.0 does not restrict access to its vendor-orders endpoint, allowing any authenticated user to read all WooCommerce orders and customer personal information. This can lead to unauthorized access to sensitive information, including customer data. The plugin's lack of access control allows Subscribers and other authenticated users to exploit this vulnerability. Defenders should verify and restrict access to the vendor-orders endpoint, limit access to sensitive order information, and monitor for unauthorized access attempts.

Defensive priority

Authenticated users can access sensitive order information; verify and restrict access to vendor-orders endpoint.

Recommended defensive actions

  • Verify and restrict access to the vendor-orders endpoint
  • Limit access to sensitive order information
  • Monitor for unauthorized access attempts
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.

Evidence notes

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. Evidence is limited; defenders should verify affected versions, review access controls, and monitor for unauthorized access attempts.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-16039 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-16039

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-16039 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-16039

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.