dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-10731

CRITICAL · 9.3 CVSS v4.0 Published 2026-06-09
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
SQL injection in the ‘two_steps_auth_code’ parameter processed by the ‘twoStepsAuthVerification’ function within the ‘/user-login’ endpoint. The two-factor authentication (2FA) functionality can be accessed without prior authentication, allowing unauthenticated attackers to execute arbitrary SQL queries on the backend database. A successful exploit could lead to database enumeration, the unauthorised creation of privileged users, the modification or deletion of critical information, and denial-of-service conditions.

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 the two-factor authentication verification function (twoStepsAuthVerification) at the /user-login endpoint allows unauthenticated attackers to inject malicious SQL through the two_steps_auth_code parameter, enabling arbitrary database queries due to the 2FA functionality being accessible without prior authentication.

MitigationFix by implementing proper authentication checks before allowing 2FA verification access and replacing dynamic SQL construction with parameterized queries/prepared statements for the two_steps_auth_code parameter.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 if the /user-login endpoint exists
    Scan your application for the /user-login endpoint and verify if it accepts a 'two_steps_auth_code' parameter in the request (POST or GET).
    Affected if The endpoint exists and accepts the two_steps_auth_code parameter without validation.
  2. Determine if 2FA verification allows unauthenticated access
    Attempt to access the two-factor authentication verification flow directly without completing prior authentication steps (such as username/password).
    Affected if The 2FA verification can be reached and the twoStepsAuthVerification function executes without requiring prior successful authentication.
  3. Inspect the twoStepsAuthVerification function code
    Locate the twoStepsAuthVerification function in your codebase and review how the 'two_steps_auth_code' parameter is handled before being used in database queries.
    Affected if The function uses the two_steps_auth_code parameter directly in SQL queries without parameterized queries (prepared statements) or input sanitization.
  4. Check for SQL injection vulnerabilities in the parameter handling
    Review all database queries involving the two_steps_auth_code parameter and verify if string concatenation or unsafe interpolation is used instead of bound parameters.
    Affected if SQL queries concatenate or interpolate the two_steps_auth_code parameter directly into the query string.
  5. Compare your deployed version against latest release
    Identify your application's version from the deployment artifacts or application metadata, then compare it to the latest version that includes the security fix for this CVE.
    Affected if Your deployed version predates the patch for CVE-2026-10731.

You are affected if the /user-login endpoint exposes two-step authentication that can be accessed without prior authentication and the two_steps_auth_code parameter is used in SQL queries without parameterized 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

Fix by implementing proper authentication checks before allowing 2FA verification access and replacing dynamic SQL construction with parameterized queries/prepared statements for the two_steps_auth_code parameter.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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