dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-3594

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 Riaxe Product Customizer plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.4 via the '/wp-json/InkXEProductDesignerLite/orders' REST API endpoint. The endpoint is registered with 'permission_callback' set to '__return_true', meaning no authentication or authorization checks are performed. The endpoint queries WooCommerce order data from the database and returns it to the requester, including customer first and last names, customer IDs, order IDs, order totals, order dates, currencies, and order statuses. This makes it possible for unauthenticated attackers to extract sensitive customer and order information from the WooCommerce store.

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

The Riaxe Product Customizer plugin for WordPress registers a REST API endpoint at '/wp-json/InkXEProductDesignerLite/orders' with 'permission_callback' set to '__return_true', bypassing all authentication. This allows any unauthenticated attacker to query WooCommerce order data and extract sensitive customer PII including first/last names, customer IDs, order IDs, totals, dates, currencies, and order statuses.

MitigationImplement proper authentication/authorization checks on the vulnerable REST API endpoint (replace '__return_true' with appropriate capability checks), or disable the endpoint entirely if not required. Verify WooCommerce order data is no longer accessible without authentication.

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 checks

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

  1. Verify the Riaxe Product Customizer plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Riaxe Product Customizer' or 'InkXE Product Designer Lite', or check the wp-content/plugins directory for a folder containing 'inkxe' or 'riaxe' or 'product-designer' in the name
    Affected if The plugin is installed and active
  2. Confirm WooCommerce is active
    Navigate to WordPress admin > Plugins and verify WooCommerce is installed and active, since the vulnerability exposes WooCommerce order data
    Affected if WooCommerce is active alongside the vulnerable plugin
  3. Test unauthenticated access to the REST API endpoint
    Send a GET request to /wp-json/InkXEProductDesignerLite/orders using curl or a browser (while logged out): curl -s https://yourdomain.com/wp-json/InkXEProductDesignerLite/orders
    Affected if The endpoint returns HTTP 200 and displays JSON containing order data (customer names, IDs, totals, dates, currencies, statuses) without requiring login credentials
  4. Check the plugin version
    In WordPress admin > Plugins, click on the plugin to view its version number, or inspect the main plugin file header in wp-content/plugins/.../index.php or similar
    Affected if The installed version matches any vulnerable version of the plugin (compare against official release notes or security advisories)
  5. Inspect the permission_callback in the REST API registration
    Locate the plugin file that registers the REST route (typically in the main plugin file or a rest-api folder) and search for 'register_rest_route' with 'InkXEProductDesignerLite/orders', then verify the permission_callback parameter is set to '__return_true'
    Affected if The endpoint uses '__return_true' or a function that always returns true as the permission_callback, indicating the vulnerability is present

A user is affected if the Riaxe Product Customizer plugin is installed with WooCommerce active AND the endpoint /wp-json/InkXEProductDesignerLite/orders returns order data without requiring authentication.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authentication/authorization checks on the vulnerable REST API endpoint (replace '__return_true' with appropriate capability checks), or disable the endpoint entirely if not required. Verify WooCommerce order data is no longer accessible without authentication.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3594 — 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-2026-3594 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