CVE-2026-40810
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 · uneditedAn unauthenticated remote attacker can exploit an unauthenticated SQL Injection vulnerability in the userinfo endpoint 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 · high confidenceAn unauthenticated remote attacker can exploit a SQL Injection vulnerability in the userinfo endpoint. The application fails to properly neutralize special elements in SQL SELECT commands, allowing attackers to inject malicious SQL queries. This can lead to total confidentiality loss by extracting sensitive data from the database.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the application and versionLocate the application binary or package and determine its installed version using system commands (e.g., rpm -q, dpkg -l, or checking the application's --version flag)Affected if The installed version is unknown or falls within an affected range that includes this SQL injection vulnerability
-
Confirm the userinfo endpoint existsCheck if the web application exposes a /userinfo or userinfo endpoint by reviewing the application's routing configuration, URL mappings, or by attempting to access it via HTTP requestAffected if The userinfo endpoint is present and accessible without authentication
-
Inspect the userinfo endpoint code for SQL query constructionReview the source code or decompile the application to examine how SQL queries are constructed in the userinfo endpoint handler. Look for string concatenation or string formatting used to build SELECT statements with user-supplied inputAffected if The code uses dynamic SQL construction (string concatenation, format strings) to incorporate request parameters into SELECT queries without parameterized queries or prepared statements
-
Verify database user privilegesCheck the database account used by the application. If the application database user has excessive privileges (e.g., is a database admin, has SELECT on system tables), the impact of SQL injection is greaterAffected if The application database user has broad database access beyond what is required for normal operation
-
Check for WAF or input validation layersReview any web application firewall, reverse proxy, or application-level input validation that may be inspecting or blocking SQL injection attempts on the userinfo endpointAffected if No WAF or input validation is present, or existing rules do not specifically block SQL injection in the userinfo endpoint parameters
The environment is affected if the userinfo endpoint is exposed and the application constructs SQL queries dynamically (without parameterized queries or prepared statements) using user-supplied input.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace dynamic SQL queries with parameterized queries or prepared statements in the userinfo endpoint to properly neutralize user input before including it in SQL commands.
- Consultation4.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40810 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-40810 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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