Blog

"Prevention is cheaper than a breach"

Home / Threats / CVE-2026-12493

CVE-2026-12493 - Before 1 Plugin

CVE-2026-12493

The Clover Payment Gateway by Zaytech for WooCommerce WordPress plugin before 1.3.6 does not verify that an approved external payment record actually belongs to the WooCommerce order being completed, nor that the paid amount matches the order total, allowing unauthenticated users to mark arbitrary orders as paid by replaying a single genuinely-approved payment reference (for example one obtained from their own minimal purchase).

CVE-2026-12493

UNKNOWN CVSS 0.0 Published 2026-07-27 Updated 2026-07-27
AI Risk Low (14/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P5 Monitor
Severity Band UNKNOWN
CVSS Vector Unspecified
Affected Components 2
Reference Links 1
AI Risk Engine Low (14/100)
Exploitability High
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-07-27 CVE published and first recorded in the threat feed.
  2. 2026-07-27 Record updated with latest vulnerability metadata.
  3. 2026-07-27 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 2 hours ago

AI enriched 2 hours ago (2026-07-27 20:15 UTC)

Technical Summary

The Clover Payment Gateway by Zaytech for WooCommerce WordPress plugin before 1.3.6 does not verify that an approved external payment record actually belongs to the WooCommerce order being completed, nor that the paid amount matches the order total, allowing unauthenticated users to mark arbitrary orders as paid by replaying a single genuinely-approved payment reference (for example one obtained from their own minimal purchase).

Potential Impact

Severity is UNKNOWN (CVSS 0.0). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on remote code execution potential, low-bar exploit prerequisites.

Primary risk drivers: remote code execution potential, low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 14/100 (Low, High) with priority P5 Monitor. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Scroll to top