CVE-2026-2592
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Zarinpal Gateway for WooCommerce plugin for WordPress is vulnerable to Improper Access Control to Payment Status Update in all versions up to and including 5.0.16. This is due to the payment callback handler 'Return_from_ZarinPal_Gateway' failing to validate that the authority token provided in the callback URL belongs to the specific order being marked as paid. This makes it possible for unauthenticated attackers to potentially mark orders as paid without proper payment by reusing a valid authority token from a different transaction of the same amount.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Zarinpal Gateway for WooCommerce plugin's payment callback handler 'Return_from_ZarinPal_Gateway' does not validate that the authority token in the callback URL corresponds to the specific order being marked as paid, allowing unauthenticated attackers to potentially mark arbitrary orders as paid by reusing valid authority tokens from other transactions of the same amount.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Zarinpal Gateway plugin is installedLocate the plugin directory in the WordPress plugins folder (typically wp-content/plugins/) and verify a folder matching 'zarinpal' or 'Zarinpal' existsAffected if The plugin directory is present on the server
-
Check the installed plugin versionOpen the main plugin PHP file and locate the version comment in the file header, or check the plugin version via WordPress admin under Plugins > Installed PluginsAffected if The version number is lower than 5.0.17 (the version with the fix)
-
Verify the plugin is activeCheck WordPress admin under Plugins > Installed Plugins to see if the Zarinpal Gateway plugin is activated, or query the wp_options table for the active_plugins optionAffected if The plugin shows as active in WordPress
-
Confirm WooCommerce is activeCheck WordPress admin under Plugins > Installed Plugins to verify WooCommerce is activated, as this plugin requires WooCommerce to process paymentsAffected if WooCommerce is active and the Zarinpal plugin is enabled
-
Check callback endpoint accessibilityExamine the plugin code to identify the callback handler function 'Return_from_ZarinPal_Gateway' and determine if it is registered as a hook (typically via add_action or add_shortcode)Affected if The callback handler is registered and the plugin handles return URLs from Zarinpal
If the Zarinpal Gateway for WooCommerce plugin is installed, active, running version lower than 5.0.17, and WooCommerce is enabled, the environment is likely affected by this authorization bypass vulnerability in the payment callback handler.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate to version 5.0.17 or later which implements proper authority token validation to ensure the token belongs to the specific order before updating payment status.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2592 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2592 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data