dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-3599

HIGH · 7.5 CVSS v3.1 Published 2026-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 SQL Injection via the 'options' parameter keys within 'product_data' of the /wp-json/InkXEProductDesignerLite/add-item-to-cart REST API endpoint in all versions up to, and including, 2.1.2. This is due to insufficient escaping on the user-supplied parameter and insufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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

Unauthenticated SQL injection in the Riaxe Product Customizer (InkXE Product Designer Lite) WordPress plugin. The vulnerability exists in the /wp-json/InkXEProductDesignerLite/add-item-to-cart REST API endpoint where the 'options' parameter within 'product_data' is not properly sanitized or escaped before being used in SQL queries, allowing attackers to inject malicious SQL commands.

MitigationUpdate the plugin to a version beyond 2.1.2 if available; otherwise, implement parameterized queries/prepared statements for all SQL queries using the 'options' parameter and add proper input validation on the REST API endpoint.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 plugin is installed
    Check for the InkXE Product Designer Lite plugin in your WordPress installation: navigate to wp-content/plugins/ or check via WordPress admin dashboard under Plugins
    Affected if The plugin Riaxe Product Customizer / InkXE Product Designer Lite is present in the WordPress installation
  2. Identify the installed plugin version
    Read the main plugin file (usually inkxe-product-designer-lite.php or similar in wp-content/plugins/) and locate the version header comment, or check the plugin row in WordPress admin Plugins page
    Affected if The version is 2.1.2 or lower, since the fix is reportedly beyond 2.1.2
  3. Confirm the vulnerable REST API endpoint exists
    Check if the file handling the REST route exists in the plugin directory, typically look for files that register the /wp-json/InkXEProductDesignerLite/add-item-to-cart endpoint
    Affected if The REST endpoint /wp-json/InkXEProductDesignerLite/add-item-to-cart is registered and accessible without authentication
  4. Inspect the SQL query handling for the options parameter
    Examine the plugin PHP files that process the add-item-to-cart REST endpoint, specifically look for SQL queries using the 'options' parameter from 'product_data' without prepared statements
    Affected if The code uses the 'options' parameter directly in SQL queries without parameterized queries or proper escaping
  5. Test unauthenticated access to the endpoint
    Send a crafted POST request to /wp-json/InkXEProductDesignerLite/add-item-to-cart with a test payload in the 'options' parameter to observe if the endpoint processes it without authentication
    Affected if The endpoint accepts unauthenticated requests and processes the 'options' parameter without sanitization

A user is affected if the InkXE Product Designer Lite plugin is installed with version 2.1.2 or lower AND the REST API endpoint /wp-json/InkXEProductDesignerLite/add-item-to-cart is accessible without authentication and processes the 'options' parameter in SQL queries without prepared statements.

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

Update the plugin to a version beyond 2.1.2 if available; otherwise, implement parameterized queries/prepared statements for all SQL queries using the 'options' parameter and add proper input validation on the REST API endpoint.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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