CVE-2026-66468
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 · uneditedUnauthenticated Cross Site Scripting (XSS) in Local Delivery Drivers for WooCommerce <= 3.0.0 versions.
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 analysisUntrusted input is placed into a web page without being neutralised, so an attacker's markup or script executes in another user's browser. That can hijack sessions, capture keystrokes, or silently perform actions as the victim. Fixing it properly means context-aware output encoding everywhere data meets HTML, backed by a content-security policy as a second line of defence.
General guidance for the cross-site scripting (xss) class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
dbcve · scopedPlugin version > 3.0.0 (check WordPress plugin repository for latest stable release)
- 1. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- 2. Locate 'Local Delivery Drivers for WooCommerce' in the plugin list
- 3. Check the current installed version number
- 4. If version is 3.0.0 or lower, update the plugin to the latest available version
- 5. Verify the update completed successfully
- 6. Test the delivery driver functionality to confirm normal operation
Generated from the published advisory — verify against the referenced sources before acting.
There is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $3,100. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-66468 — 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 sourcesCVE-2026-66468 describes a stored XSS vulnerability in Local Delivery Drivers for WooCommerce (versions <= 3.0.0) with a CVSS 3.1 base score of 7.1 and an EPSS score of 0.0018. These two numbers are telling you something important: the theoretical severity is moderate, but the probability of automated exploitation in the next 30 days is effectively zero. For practical prioritization, trust the EPSS over the CVSS here. The 'unauthenticated' classification in the WordPress plugin ecosystem warrants scrutiny you won't get from the CVE alone. This plugin creates custom roles—drivers, dispatchers, delivery managers—outside WordPress core's permission model. 'Unauthenticated' may not mean 'public-facing input accepts unsanitized data' but rather 'a role-check within the plugin's custom capability system can be bypassed.' These are different vulnerability classes with different remediation paths: the first needs input sanitization; the second needs a full review of the plugin's role-permission model. The more immediate operational concern is whether a patched version actually exists. The version constraint 'versions <= 3.0.0' typically signals that 3.0.0 is the highest affected release and fixes live above it—but you should verify that a 3.0.1 or later release has been published before generating remediation tickets. If no fixed version exists, your response shifts from 'apply the patch' to 'evaluate compensating controls or migrate to an active alternative,' which is a fundamentally different decision tree. The WooCommerce integration matters for impact assessment even when exploitation probability is low. This plugin touches order records, driver data, and delivery confirmations—an admin-context XSS here can pivot into the broader WooCommerce data layer containing customer PII, shipping addresses, and transaction history. The EPSS says this won't be exploited tomorrow. But if it ever is, the blast radius extends well beyond the plugin itself. Finally, the future-dated CVE identifier (CVE-2026-66468) suggests this may be a pre-disclosure placeholder or an incompletely coordinated release. This means automated scanners may flag the vulnerability before full remediation details are available, creating alert fatigue without actionable guidance. Treat the EPSS as your operational anchor until the patch situation clarifies.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-66468 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