dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-40839

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
An low privileged remote attacker can exploit an unauthenticated SQL Injection vulnerability in the getComponentScalings function due to improper neutralization of special elements in a SQL SELECT command. This can result in a total loss of confidentiality.

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 confidence

A SQL injection vulnerability exists in the getComponentScalings function where user-supplied input is not properly neutralized before being used in a SQL SELECT query. This allows unauthenticated remote attackers with low privileges to inject malicious SQL commands, resulting in unauthorized data access and total loss of confidentiality.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements to properly neutralize user input. Apply least-privilege principles to database accounts and validate all input before database interactions.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify product and version
    Locate the application's version information in installation directories, configuration files, or the application's about/status page. Compare against any available version documentation.
    Affected if The installed version falls within an affected range (if such ranges become available) or is an unpatched version of the software containing the getComponentScalings function.
  2. Locate the getComponentScalings function
    Search the application source code for the function named 'getComponentScalings' - this may be in Java, PHP, Python, or other language source files depending on the application framework.
    Affected if The function exists in the codebase and handles user-supplied input without proper sanitization.
  3. Inspect SQL query construction in getComponentScalings
    Examine the getComponentScalings function code to see how SQL SELECT queries are built. Look for string concatenation or string formatting (e.g., + operator, f-strings, String.format) used to construct SQL statements.
    Affected if Dynamic SQL queries are constructed using string concatenation or formatting with user input rather than parameterized queries.
  4. Verify input validation and parameterization
    Review the code paths that feed input into getComponentScalings. Check if input is validated, sanitized, or passed as bound parameters to a PreparedStatement or equivalent.
    Affected if User-supplied parameters are passed directly into SQL queries without using parameterized queries, prepared statements, or input validation/sanitization.
  5. Assess authentication and authorization requirements
    Determine if the getComponentScalings endpoint/function requires authentication and what privilege level is needed to access it.
    Affected if The vulnerable function is accessible to unauthenticated users or to users with low privileges, allowing remote attackers to exploit the SQL injection.

The environment is affected if the application contains the getComponentScalings function and uses dynamic SQL query construction with user input without parameterization, particularly if the function is accessible to unauthenticated or low-privilege users.

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

Replace dynamic SQL queries with parameterized queries or prepared statements to properly neutralize user input. Apply least-privilege principles to database accounts and validate all input before database interactions.

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

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 locally
dbcve dependency scanner

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