CVE-2026-9612
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 · uneditedThe WhatsOrder – Instant Checkout for WooCommerce plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.0.1 via the yapacdev_generate_order_pdf. This makes it possible for unauthenticated attackers to extract sensitive customer PII and order details — including full name, email address, phone number, billing address, ordered items with quantities and prices, applied coupons, shipping method, and order total — from any customer's invoice by enumerating sequential order IDs. Invoice HTML files are written to the publicly accessible wp-content/uploads/whatsorder_invoices/ directory, which is created without an .htaccess deny rule or index.php guard, making every invoice directly downloadable over HTTP with no authentication check.
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 confidenceThe WhatsOrder plugin for WordPress writes invoice HTML files to a publicly accessible directory (wp-content/uploads/whatsorder_invoices/) without .htaccess restrictions or index.php guards. An unauthenticated attacker can download any customer's invoice by enumerating sequential order IDs, exposing full names, email addresses, phone numbers, billing addresses, order items, quantities, prices, coupons, shipping methods, and order totals.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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.
-
Verify WhatsOrder plugin is installedCheck WordPress plugins directory or wp-content/plugins/ for a folder named 'whatsorder' or similar. Also check via WordPress admin under Plugins > Installed Plugins.Affected if The WhatsOrder plugin is present on the WordPress site
-
Confirm vulnerable invoice directory existsCheck if the directory wp-content/uploads/whatsorder_invoices/ exists on the server filesystem using file manager, FTP, or SSH.Affected if The directory wp-content/uploads/whatsorder_invoices/ exists and contains invoice files
-
Check for missing .htaccess protectionInspect the wp-content/uploads/whatsorder_invoices/ directory for an .htaccess file. If present, verify it contains 'deny from all' or similar restrictions. If absent, the directory is unprotected.Affected if No .htaccess file with deny rules exists in the whatsorder_invoices directory
-
Check for missing index.php guardVerify there is no index.php file inside wp-content/uploads/whatsorder_invoices/ that could prevent directory listing.Affected if No index.php file is present in the whatsorder_invoices directory
-
Test invoice accessibility via webAttempt to access a known or guessed invoice file via browser: visit https://yourdomain.com/wp-content/uploads/whatsorder_invoices/ and try enumerating order IDs (e.g., /invoice_1.html, /invoice_001.html).Affected if Invoice files are downloadable without authentication
A site is affected if the WhatsOrder plugin is installed and the wp-content/uploads/whatsorder_invoices/ directory is publicly accessible without .htaccess or index.php protection, allowing unauthenticated enumeration of customer invoice files.
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 dataImmediately restrict or remove the publicly accessible wp-content/uploads/whatsorder_invoices/ directory by adding .htaccess deny rules or moving it outside the webroot. Disable the vulnerable yapacdev_generate_order_pdf function until a patched plugin version is available.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9612 — 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-9612 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