dbcve.org
Order Delivery Date For Wp E CommerceWordPress extension · Tychesoftwares

CVE-2024-0678

MEDIUM · 6.1 CVSS v3.1 Published 2024-02-05
Fix available
A fix is available. Upgrade to after 1.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
The Order Delivery Date for WP e-Commerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'available-days-tf' parameter in all versions up to, and including, 1.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Please note this only affects the version of the "order-delivery-date" plugin for WP Ecommerce which was hosted in the WordPress repository and is discontinued now. The version of the plugin hosted off of the repository titled 'Order Delivery Date' for WooCommerce is not affected.

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 confidence

Stored XSS vulnerability in the Order Delivery Date plugin for WP e-Commerce. The 'available-days-tf' parameter lacks proper input sanitization and output escaping, allowing unauthenticated attackers to inject malicious JavaScript that executes when users access affected pages.

MitigationSince the plugin is discontinued and no longer maintained, the recommended approach is to remove it entirely. If continued use is required, implement proper input sanitization (sanitize_text_field) and output escaping (esc_attr/esc_html) on the 'available-days-tf' parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Order Delivery Date For Wp E CommerceWordPress extension
Affected:<= 1.2

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify the plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'Tychesoftwares Order Delivery Date For Wp E Commerce' in the installed plugins list
    Affected if The plugin appears in the installed plugins list
  2. Check the installed version
    In the Plugins list, click on the plugin details or view the readme.txt file in the plugin directory (/wp-content/plugins/order-delivery-date-for-wp-e-commerce/) to determine the version number
    Affected if Version is 1.2 or lower (any version <= 1.2)
  3. Identify if the vulnerable parameter is in use
    Check the plugin settings page for any form fields using the parameter name 'available-days-tf' - typically found in delivery date configuration or availability settings
    Affected if The 'available-days-tf' parameter field exists and is accessible in the plugin settings
  4. Inspect stored parameter value for potential XSS payloads
    Examine the database table wp_options (or equivalent prefixed table) for option_name containing 'available-days-tf' and inspect the option_value for unsanitized HTML or script tags
    Affected if The stored value contains unescaped HTML tags, script elements, or JavaScript event handlers (e.g., <script>, onerror=, onload=)

A user is affected if the plugin is installed with version 1.2 or lower AND the 'available-days-tf' parameter field exists in their configuration with unsanitized content stored in the database.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.2
Interim mitigation

Since the plugin is discontinued and no longer maintained, the recommended approach is to remove it entirely. If continued use is required, implement proper input sanitization (sanitize_text_field) and output escaping (esc_attr/esc_html) on the 'available-days-tf' parameter.

Recommended fix High confidence
  1. 1. This plugin (Order Delivery Date for WP e-Commerce) is discontinued and no longer maintained.
  2. 2. Uninstall the affected plugin: Order Delivery Date for WP e Commerce (version <= 1.2)
  3. 3. Migrate to an actively maintained alternative delivery date plugin compatible with your e-commerce solution
  4. 4. If migration is not immediately possible, disable the plugin entirely to prevent exploitation
  5. 5. Review any custom code that may reference the 'available-days-tf' parameter and remove it
Caveat Plugin is discontinued with no available fix; requires migration to alternative solution

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Order Delivery Date For Wp E Commerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0678 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-0678 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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