Security readout for executives and security teams
Plain-English summary
This flaw affects the Zarinpal Gateway for WooCommerce WordPress plugin through version 5.0.16. An unauthenticated attacker may be able to make an order appear paid without completing the correct payment, by reusing a valid payment authority token from another same-amount transaction. The business risk is fraudulent order fulfillment and reconciliation issues.
Executive priority
Treat as urgent for affected online stores because it can cause unpaid orders to be marked paid. Prioritize patching, payment reconciliation, and fraud review over general WordPress hardening tasks.
Technical view
The callback handler Return_from_ZarinPal_Gateway does not validate that the authority token in the callback URL belongs to the specific WooCommerce order being marked paid. CVSS is 7.7 high, with network access, no authentication, and high attack complexity. Sources reference WordPress plugin code locations and a WordPress.org changeset.
Likely exposure
Exposure is limited to WordPress/WooCommerce stores using the Zarinpal Gateway plugin at version 5.0.16 or earlier. Internet-facing checkout flows using this payment method are the relevant target surface.
Exploitation context
No CISA KEV listing is provided, and the source bundle does not state active exploitation. The attack requires a valid authority token from another transaction of the same amount, which raises complexity but does not require login.
Researcher notes
The key issue is authorization binding, not payment cryptography: the callback trusts an authority value without confirming it maps to the order being completed. Evidence is from the CVE description, Wordfence entry, plugin code references, and WordPress.org changeset.
Mitigation direction
- Update the Zarinpal Gateway plugin to a vendor-fixed release newer than 5.0.16 when available.
- Review the WordPress.org changeset and vendor guidance before deploying the fix.
- Reconcile recent Zarinpal-paid WooCommerce orders against actual payment settlement records.
- Increase review of same-amount orders and payment callbacks until patched.
Validation and detection
- Inventory WooCommerce sites for the Zarinpal Gateway plugin.
- Confirm whether installed versions are 5.0.16 or earlier.
- Verify updated code binds the callback authority token to the specific order.
- Compare WooCommerce paid orders with Zarinpal settlement records.
- Check logs for unusual payment callbacks or repeated authority-token patterns.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-2592 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:H2.25.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.7HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/e33fcd17-318b-408e-86bf-b4ece46121cc?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/zarinpal-woocommerce-payment-gateway/trunk/class-wc-gateway-zarinpal.php#L359CVE reference
- https://plugins.trac.wordpress.org/changeset/3445917/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.