dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-25371

CRITICAL · 9.3 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in King-Theme Lumise Product Designer lumise allows Blind SQL Injection.This issue affects Lumise Product Designer: from n/a through < 2.0.9.

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

SQL Injection vulnerability in Lumise Product Designer allows attackers to inject malicious SQL queries through unsanitized user inputs. The 'Blind' variant means the attacker cannot see direct query results but can infer information through application behavior differences. This critical flaw enables potential database compromise, including data exfiltration, modification, or destruction.

MitigationUpgrade Lumise Product Designer to version 2.0.9 or later. Prior to upgrade, audit and sanitize all database query paths, implement parameterized queries/prepared statements, and apply least-privilege database user restrictions.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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 checks

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

  1. Identify Lumise Product Designer installation
    Search for lumise-related files, directories, or components in the web root (e.g., /wp-content/plugins/lumise/, /lumise/, or check CMS plugin listings if WordPress)
    Affected if Lumise Product Designer is found installed on the system
  2. Determine installed Lumise version
    Check version file or header in the Lumise installation directory (commonly lumise.php, package.json, or version defined in main plugin file)
    Affected if Installed version is lower than 2.0.9 or version cannot be determined
  3. Verify database query execution paths exist
    Inspect Lumise source code for direct SQL query execution via $wpdb->query, mysql_query, mysqli_query, or similar without prepared statements in lumise core files (e.g., in includes/ or src/ folders)
    Affected if SQL queries are built using string concatenation with user input without parameterization
  4. Check for unsanitized user input usage in queries
    Review code for $_GET, $_POST, $_REQUEST, or similar superglobals passed directly into SQL queries without escaping or parameter binding
    Affected if User-supplied input flows directly into SQL statements without sanitization or prepared statements
  5. Review web server logs for SQL injection patterns
    Search access logs for unusual SQL syntax in Lumise-related requests (e.g., UNION SELECT, OR 1=1, time-based blind injection like SLEEP)
    Affected if Suspicious SQL patterns are found in logs referencing Lumise endpoints

If Lumise Product Designer is installed and the version is below 2.0.9 with direct SQL query construction using unsanitized input, the environment is affected by this vulnerability.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Lumise Product Designer to version 2.0.9 or later. Prior to upgrade, audit and sanitize all database query paths, implement parameterized queries/prepared statements, and apply least-privilege database user restrictions.

Recommended fix Moderate confidence

2.0.9 or later

  1. 1. Backup your entire website database and files before making any changes
  2. 2. Navigate to your WordPress admin dashboard > Appearance > Themes (or Plugins section depending on installation method)
  3. 3. Locate the Lumise Product Designer theme/plugin
  4. 4. Check current installed version to confirm it is below 2.0.9
  5. 5. Update to version 2.0.9 or the latest available version
  6. 6. Verify the update was successful by checking the version number
  7. 7. Test the product designer functionality to ensure it works correctly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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