Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site running vulnerable plugin
-
DeliverySend crafted unauthenticated handler request
-
ExploitSupply arbitrary wp_options name
-
ExecutionPlugin deletes option without authorization
-
ImpactSite configuration destroyed, site offline
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires only that a target run the zipMoney (Zip Co) Payments Plugin for WooCommerce at a version below 2.4.0 with its vulnerable front-end request handler reachable - the default state. No authentication, no user interaction, and no special configuration are needed (PR:N/UI:N); the attacker simply supplies an arbitrary option name to the unprotected handler. The only meaningful limit on exploitation is plugin presence and version: sites on 2.4.0+ or without the plugin are unaffected, and the impact is destruction/availability (integrity and availability) rather than data theft. |
| Impact | The signals are mixed but lean toward genuine priority within affected installations. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, C:N/I:H/A:H, score 9.1) describes trivial remote unauthenticated exploitation with high integrity and availability impact but no confidentiality loss, which matches the description precisely. SSVC reports Exploitation: none (no observed in-the-wild activity), Automatable: yes (reconnaissance and exploitation can be scripted across many sites), and Technical Impact: partial - the 'partial' rating is arguably conservative given that deleting access-control options can take an entire site offline. Publicly available exploit code raises real-world risk, though POC availability is distinct from active exploitation, which is not confirmed (not in CISA KEV). EPSS is not provided in the input. The dominant limiting factor is footprint: this is a niche regional payment plugin, so automatable mass exploitation is bounded by how many sites actually run it. |
| Exploit ScenarioDerived | An attacker scans WordPress sites for the vulnerable plugin, then sends a single crafted unauthenticated front-end request invoking the handler with option names such as the active_plugins or site access-control entries. The plugin deletes those options without any authorization check, deactivating the plugin fleet-wide and corrupting site configuration so the site goes offline. Public exploit code exists, making this scriptable at scale. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 10, 2026
Unauthenticated arbitrary WordPress option deletion in the zipMoney (Zip Co) Payments Plugin for WooCommerce before 2.4.0 lets remote attackers destroy site configuration and take the site offline. One front-end request handler performs no authorization checks and does not restrict which option name the caller supplies, so any unauthenticated visitor can delete critical wp_options entries. Publicly available exploit code exists and a vendor patch (2.4.0) is available; no active exploitation has been confirmed (not in CISA KEV).
RemediationAI
Apply the primary fix by upgrading to zipMoney (Zip Co) Payments Plugin for WooCommerce 2.4.0 or later (Vendor-released patch: 2.4.0), which adds the missing authorization/nonce check on the request handler. If immediate patching is not possible, compensating controls include deactivating and removing the plugin entirely (trade-off: disables Zip Co payments at checkout), or using a WAF/web-server rule to block unauthenticated requests to the plugin's vulnerable front-end handler endpoint (trade-off: must correctly identify the action parameter and may break legitimate checkout calls if over-broad). Because exploitation deletes wp_options, ensure current database backups exist before and after remediation so a site can be restored if already tampered with. See the WPScan advisory (https://wpscan.com/vulnerability/8b9a00f5-d7f5-447d-b109-d15e2cde3885/) for specifics.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is a WooCommerce payment gateway plugin for WordPress that integrates the zipMoney (Zip Co) buy-now-pay-later service. The root cause is CWE-862 (Missing Authorization): one of the plugin's front-end AJAX/request handlers is registered so that it is reachable by unauthenticated callers and omits both a capability/nonce check and any allow-list on the option name argument. Because WordPress stores nearly all site and plugin state in the wp_options table (accessed via delete_option), an attacker-controlled option name lets the handler delete any option - including access-control, site URL, active_plugins, and configuration values. The CPE is cpe:2.3:a:unknown:zipmoney(zip_co)_payments_plugin_for_woocommerce:*, with the vendor string left as the placeholder 'unknown'.
Know when Zipmoney Zip Co Payments Plugin For Woocommerce gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
Remote unauthenticated request with no interaction deletes arbitrary options (I:H) and can take the site offline (A:H); no data disclosure so C:N.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
3DescriptionCVE.org
The zipMoney(Zip Co) Payments Plugin for WooCommerce WordPress plugin before 2.4.0 does not perform any authorisation checks on one of its front-end request handlers, and does not restrict which option name a caller may supply, allowing unauthenticated users to delete arbitrary WordPress options. This can be used to destroy site and access control configuration, deactivate every installed zipMoney(Zip Co) Payments Plugin for WooCommerce WordPress plugin before 2.4.0, and take the site offline.
Articles & Coverage 1
Technical POC Analysis
The bug class is CWE-862: Missing Authorization.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
The zipMoney Payments Plugin for WooCommerce (versions before 2.4.0) contains a critical vulnerability allowing unauthenticated attackers to delete essential WordPress configuration and take the site offline. Publicly available exploit code exists, creating significant risk for organizations using this plugin; immediate patching is required to prevent potential attacks.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-75265
GHSA-rx27-rpmw-vv8g
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB