CVE-2026-24946
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 · uneditedMissing Authorization vulnerability in tychesoftwares Print Invoice & Delivery Notes for WooCommerce woocommerce-delivery-notes allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Print Invoice & Delivery Notes for WooCommerce: from n/a through <= 5.8.0.
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 confidenceMissing Authorization vulnerability in the Print Invoice & Delivery Notes plugin for WooCommerce allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to print or download invoice and delivery note documents.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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.
-
Identify the plugin installationLocate the 'print-invoice-delivery-notes' or 'woocommerce-delivery-notes' folder in wp-content/plugins/ directory, or query the WordPress plugins API: GET /wp-json/wp/v2/plugins?search=invoiceAffected if The plugin is installed and active in WordPress/WooCommerce
-
Determine the installed versionCheck the main plugin PHP file for the 'Version' header comment, or query: GET /wp-json/wp/v2/plugins?search=invoice (response field 'version')Affected if Version is lower than 5.8.1 or cannot be determined (unknown versions may still be vulnerable)
-
Identify the vulnerable endpointsCommon endpoints for this plugin include: /?print_delivery_note=true, /?action=print_delivery_note, /wp-content/plugins/woocommerce-delivery-notes/print/print.php, or similar paths under /?page=wc_delivery_notes&printInvoice=trueAffected if Endpoints exist and respond to requests (plugin is installed)
-
Test endpoint authorizationSend unauthenticated HTTP requests to the identified print/download endpoints (e.g., curl -I 'https://SITE/?print_delivery_note=1') and verify if the server returns invoice/delivery note data without requiring login credentialsAffected if Unauthenticated requests return invoice or delivery note content (200 OK with PDF/HTML containing order data) instead of redirecting to login or returning 401/403
-
Verify access control configurationCheck plugin settings in WooCommerce > Settings > Print Invoice & Delivery Notes (or similar) for any 'Access Permission' or 'User Role' settings that may be misconfigured to 'Anyone' or left undefinedAffected if Access control is set to allow public/unauthenticated access, or no role restriction is configured
A user is affected if the Print Invoice & Delivery Notes plugin is installed with a version below 5.8.1 AND the print/download endpoints are accessible without authentication, allowing unauthorized access to invoice or delivery note documents.
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 version 5.8.1 or later if available; otherwise implement additional access controls at the web server or WAF level to restrict unauthorized access to the affected endpoints.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24946 — 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-2026-24946 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