VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

Cardinity Payment Gateway for WooCommerce 3.2.6 — 3.4.1 - Unauthenticated Arbitrary Order Status Manipulation

CVE-2026-103324Published · Updated

Action summary

Affected: 3.2.6 – 3.4.1Update to 3.4.2 or newer

All remediation steps
Watch plugin
Severity
Medium5.3
CVSS
5.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-602 Client-Side Enforcement of Server-Side Security
Required access
No account needed
Exploit prediction (EPSS)
0.1% chance in 30 days2th percentile
CISA KEV
Not listed
On this page8

Am I affected?

Cardinity Payment Gateway for WooCommerce cardinity-free-payment-gateway-for-woocommerce

  1. Affected3.2.6 – 3.4.1
  2. Patched in3.4.2

Update to 3.4.2 or newer.

You are affected if you run 3.2.6 – 3.4.1. Version 3.4.2 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Cardinity Payment Gateway for WooCommerce.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 3.4.2, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Cardinity Payment Gateway for WooCommerce to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Naoki Kawahigashi.

The Cardinity Payment Gateway for WooCommerce plugin for WordPress is vulnerable to Payment Bypass in versions 3.2.6 through 3.4.1. This is due to missing check for an empty project_secret before HMAC signature verification, allowing an attacker to forge a valid signature when the secret is an empty string. This makes it possible for unauthenticated attackers to forge an approved-payment notification and mark arbitrary orders as paid or failed. The Cardinity project secret setting must be left at its default empty value.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Cardinity Payment Gateway for WooCommerce

All 2
More vulnerabilities in Cardinity Payment Gateway for WooCommerce
SeverityVulnerabilityCVEPublished
Medium6.1Reflected Cross-Site Scripting
≤3.0.6Update to 3.0.7
—

Timeline

  1. CVE published

    Severity medium, CVSS 5.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
EPSS
Exploit Prediction Scoring System by FIRST.org.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?