Is CVE-2026-97219 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-97219 being exploited in the wild.

How severe is CVE-2026-97219?

Medium severity, with a CVSS score of 4.3, published 2 October 2026.

Is there a fix for CVE-2026-97219?

Yes: fixed in 4.22.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-97219 attacked?

It is attacked over the network.

Am I affected by CVE-2026-97219?

Check whether you run MStore API at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-97219: MStore API WordPress plugin payment bypass via order status

CVE-2026-97219 · Severity: medium · CVSS 4.3 · Published 2026-10-02

The MStore API WordPress plugin handles order processing for online stores. A vulnerability allows any customer with a registered account to change their unpaid order status to paid or fulfilled without actually paying, letting them obtain goods for free. This affects all installations before version 4.22.1.

Quick answers

Is CVE-2026-97219 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-97219 being exploited in the wild.
How severe is CVE-2026-97219?: Medium severity, with a CVSS score of 4.3, published 2 October 2026.
Which products and versions are affected?: MStore API before 4.22.1.
Is there a fix for CVE-2026-97219?: Yes: fixed in 4.22.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-97219 attacked?: It is attacked over the network.
Am I affected by CVE-2026-97219?: Check whether you run MStore API at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 4.22.1

Technical details

The plugin fails to validate which order fields authenticated users can modify, allowing customers to directly alter the order status field via API requests. Any user with a self-registerable account can change their own unpaid order to a paid or fulfilled state, bypassing payment validation. This is fixed in version 4.22.1.

Affected products

MStore API before 4.22.1

Timeline

2026-09-30: disclosed
2026-10-02: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.