Order Delivery Date For WoocommerceWordPress extension · Tychesoftwares
CVE-2023-41874
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in Tyche Softwares Order Delivery Date for WooCommerce plugin <= 3.20.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 analysis · moderate confidenceAn unauthenticated reflected Cross-Site Scripting (XSS) vulnerability exists in the Order Delivery Date for WooCommerce plugin by Tyche Softwares versions 3.20.0 and below. Attackers can inject malicious JavaScript code through unsanitized user input that gets reflected in web pages without proper output encoding, enabling session hijacking, credential theft, or client-side attacks.
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 WoocommerceWordPress extension
<= 3.20.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installationCheck the WordPress plugins directory at wp-content/plugins/ for the order-delivery-date-for-woocommerce folder, or view the installed plugins list in the WordPress admin dashboard under Plugins.Affected if The Order Delivery Date for WooCommerce plugin by Tyche Softwares is present in the WordPress installation
-
Determine installed versionOpen the main plugin file (order_delivery_date_for_woocommerce.php) in the plugin directory and locate the Version header in the plugin comment block at the top of the file, or check the version displayed in the WordPress admin plugins list.Affected if The reported version is 3.20.0 or lower (any version up to and including 3.20.0)
-
Identify vulnerable parametersExamine the plugin source code files that handle user input, particularly frontend-facing forms that accept order delivery date data. Look for GET or POST parameters that are directly output to HTML without using sanitization functions such as esc_html(), esc_attr(), or esc_url(). Common files to inspect include front-end submission handlers and order processing scripts.Affected if User-supplied input from frontend forms or URL parameters is reflected in page output without proper output encoding
-
Test for XSS reflectionSend a crafted request to pages utilizing the plugin's delivery date functionality, using a benign test payload such as <script>alert(1)</script> in input fields or as a URL parameter value. Observe whether the payload is executed or rendered as plain text rather than being encoded or stripped.Affected if The test payload executes as JavaScript in the browser rather than being neutralized
The environment is affected if the Tyche Softwares Order Delivery Date for WooCommerce plugin is installed with version 3.20.0 or lower and the vulnerable input parameter is accessible on the frontend.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the plugin to a version newer than 3.20.0 which contains the security patch. Until updated, consider deploying a WAF with XSS protection rules or implementing input validation/output encoding at the application level.
Fix this in Order Delivery Date For Woocommerce
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41874 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-41874 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