Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as Contributor-level user
-
ExploitInvoke plugin calendar-view AJAX action
-
ExecutionBypass missing capability check
-
ImpactRead other customers' order details
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated WordPress account with at least the Contributor role on a site running Product Delivery Date for WooCommerce below 3.3.2; the attacker then calls the plugin's calendar-view AJAX action, which lacks a capability check. This is NOT unauthenticated - the key limiting factor is that the attacker must already possess a valid low-privilege account on the target site, so exposure is confined to stores that provision Contributor-or-higher accounts to untrusted or semi-trusted users. No special plugin configuration beyond having the calendar view in use is indicated, and no user interaction is required. |
| Impact | This is a low-severity information-disclosure issue that should be treated as low priority despite multiple corroborating sources. The signals are largely consistent on the low end: CVSS base score is 2.7, EPSS is 0.15% (4th percentile) indicating very low probability of broad exploitation, and it is NOT on CISA KEV. A public exploit exists (WPScan), but POC availability is distinct from active exploitation and does not by itself elevate priority here. Note a discrepancy between the supplied CVSS vector and the description: the vector encodes PR:H (high privileges), yet the description states exploitation requires only a role 'as low as Contributor,' which is a LOW-privilege authenticated role - this points to PR:L rather than PR:H and suggests the official vector slightly overstates the privilege barrier (making the flaw marginally easier to exploit than the vector implies). The impact is confidentiality-only and partial (C:L, I:N, A:N): an attacker learns other customers' order details, with no integrity or availability effect. Realistically this matters only on multi-author/multi-role WooCommerce sites that grant Contributor+ accounts to semi-trusted users; single-admin stores have no exposure. Patch to 3.3.2 is the clear remediation. |
| Exploit ScenarioDerived | On a WooCommerce store running the plugin below 3.3.2, a user holding a Contributor-level account (e.g., a guest blogger or low-trust staff member) invokes the plugin's calendar-view AJAX action, which fails to verify capabilities and returns other customers' order information. A public exploit/PoC is documented by WPScan, and because the action is reachable over the network (AV:N) with low complexity (AC:L) and no user interaction, a logged-in low-privilege attacker can harvest order data directly. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 16, 2026
Information disclosure in the Product Delivery Date for WooCommerce WordPress plugin before 3.3.2 allows an authenticated user with only Contributor-level access to read other customers' order details via the plugin's calendar-view AJAX actions, which are missing a capability check. Publicly available exploit code exists per WPScan, but EPSS is a low 0.15% (4th percentile) and there is no confirmed active exploitation (not listed in CISA KEV). Practical exposure is limited to WooCommerce stores that grant Contributor-or-higher accounts to untrusted or semi-trusted users, since a valid low-privilege login on the target site is required.
RemediationAI
Vendor-released patch: upgrade Product Delivery Date for WooCommerce to 3.3.2 or later, which adds the missing capability check to the calendar-view AJAX actions; verify the installed version in the WordPress Plugins screen or via WP-CLI (wp plugin list) after updating, and consult the WPScan advisory at https://wpscan.com/vulnerability/d7310c1a-f858-4dc5-8102-813fb64096a6/ for the reference details. Because the flaw requires an authenticated account at Contributor level, a practical compensating control when patching must be staged is to audit and downgrade or remove Contributor-or-higher accounts that do not need them (the trade-off is that legitimate contributors lose content-editing access), and, where the calendar view is not needed, deactivate or restrict that plugin feature or block the plugin's AJAX action at the WAF/reverse-proxy layer (the trade-off is that functionality depending on those endpoints breaks). No vendor-released patch version beyond 3.3.2 is identified in the supplied data, and there is no basis to claim a fix is unavailable.
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
This is a missing-authorization flaw (CWE-200, Exposure of Sensitive Information) in a WordPress plugin. WordPress AJAX handlers registered through admin-ajax.php must call capability checks such as current_user_can() before returning data; the calendar-view AJAX action in Product Delivery Date for WooCommerce omitted that check, so any authenticated account reaching Contributor level can invoke the endpoint and receive order data belonging to other customers, including delivery-date scheduling details tied to WooCommerce orders. The CPE entry (cpe:2.3:a:unknown:product_delivery_date_for_woocommerce:*:*:*:*:*:*:*:*) marks the vendor as unknown with a wildcard version, so version identification should be done by the plugin's own header rather than by CPE matching; EUVD records affected versions as 0 up to but not including 3.3.2. The assessment vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, i.e. remote, low complexity, authenticated (PR:L), no user interaction, limited confidentiality impact only.
Know when Product Delivery Date 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:H/UI:N/S:U/C:L/I:N/A:N
Exploitation needs only a Contributor-level account per the description, so PR:L (not PR:H); network-reachable AJAX with low complexity and confidentiality-only partial disclosure gives C:L, I:N, A:N.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The Product Delivery Date for WooCommerce WordPress plugin before 3.3.2 does not perform a capability check before disclosing order details through its calendar view AJAX actions, allowing users with a role as low as Contributor to view other customers' order information.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-102698
GHSA-q562-9q87-3q47
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB