Delivery & Pickup Date Time for WooCommerce Plugin Vulnerability (CVE-2026-105328)

On this page

Security Alert Summary

The Delivery & Pickup Date Time for WooCommerce plugin contains a stored cross-site scripting (XSS) vulnerability (CVE-2026-105328). A nonce-only settings AJAX handler can store an attribute-breaking value that is later output by an administrator settings template without HTML attribute escaping. Authenticated users with subscriber-level access and above can inject scripts that execute when an injected page is viewed.


CVE Details

  • CVE ID: CVE-2026-105328
  • Affected component: Delivery & Pickup Date Time for WooCommerce plugin for WordPress
  • Affected versions: versions up to, and including, 1.3.90
  • Published: November 18, 2026 at 12:17:01 PM
  • Last modified: November 18, 2026 at 02:17:21 PM
  • CVSS v3.1: Base Score 6.4, Severity MEDIUM
    • Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
    • Attack Vector: NETWORK
    • Attack Complexity: LOW
    • Privileges Required: LOW (authenticated user required)
    • User Interaction: NONE
    • Scope: CHANGED
    • Confidentiality Impact: LOW
    • Integrity Impact: LOW
    • Availability Impact: NONE
  • Authentication / Privilege Notes: An authenticated user with low privileges (subscriber-level or higher) is sufficient to exploit the issue; no user interaction is required for the injected payload to execute once an affected page is viewed.
  • CWE / Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

Technical Details

This vulnerability is a stored cross-site scripting issue. A settings-related AJAX handler that relies only on a nonce allows an attribute-breaking value to be saved. An administrator settings template then outputs that stored value directly into HTML attributes without applying HTML attribute escaping, enabling injection of arbitrary web scripts.

The disclosure references administrative code and templates that demonstrate the issue, including files such as admin/class-coderockz-woo-delivery-admin.php and admin/partials/coderockz-woo-delivery-admin-display.php, as well as public-facing code in public/class-coderockz-woo-delivery-public.php. The core problem is the combination of a nonce-only server-side check that permits storage of unsafe input and a template that fails to escape data before inserting it into an attribute context.

Impact follows the stored XSS pattern: an attacker who can save suitable content (subscriber-level or higher) can cause script execution in the browser of any user who visits a page rendering the injected attribute. The issue affects confidentiality and integrity to a limited degree (for example, exposure or manipulation of information accessible to the victim in the browser), but it does not directly affect availability according to the CVSS data.


How This Could Impact Your Website

Consider a small ecommerce site with a site owner, internal staff (editors), and an external contractor who has a subscriber or contributor account. An authenticated attacker with a low-privilege account could save a specially crafted value via the plugin settings. When an administrator or any user with access views the affected settings page or another page that renders the stored attribute, the injected script can execute in their browser.

Practical consequences include exposure of information visible in the victim’s browser (such as internal user email addresses or session-related data presented in the page), and an increased risk of targeted phishing or social engineering using information gleaned via the injected script. The vulnerability does not necessarily imply full site compromise, but it does raise the risk to users and site data that are accessible in the browser context.

professional review If youre unsure whether your site is affected or how to assess your current user roles and plugins, it may be worth having a professional review.


Recommended Actions

  • Update the affected plugin as soon as a patched version is available.
  • Review and reduce unnecessary user roles, especially contributor and subscriber accounts that do not need write access.
  • Enforce strong passwords and enable two-factor authentication for editor and administrator accounts.
  • Remove unused or unmaintained plugins from your site.
  • Monitor site activity and logs for unusual behavior, such as unexpected changes to plugin settings or new stored content in admin screens.

If youd like help reviewing your plugins, user roles, or overall WordPress security posture, our team at Freshy is happy to help.


References