CVE-2026-51946
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 · uneditedSQL Injection vulnerability in GoAdminGroup GoAdmin (last release v1.2.26) allows a remote attacker to execute arbitrary code and obtain sensitive information via the the __sort_type URL parameter on all /admin/info/{table} endpoints
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 confidenceSQL injection vulnerability in GoAdmin v1.2.26 allows remote attackers to inject malicious SQL through the __sort_type parameter on /admin/info/{table} endpoints, potentially enabling data exfiltration or arbitrary code execution via database interaction.
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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 GoAdmin installation and versionLocate the GoAdmin application binary or source code. Check the version in go.mod file, or run the binary with a version flag if available, or inspect the admin interface footer for version displayAffected if The installed version matches 1.2.26 or falls within the affected range without a patch applied
-
Verify vulnerable endpoint accessibilityConfirm the /admin/info/{table} endpoint is accessible by attempting to access it via the web browser or curl command to the application's base URLAffected if The endpoint responds successfully, indicating it is exposed and reachable
-
Confirm __sort_type parameter acceptanceSend a request to /admin/info/{table} with a test value for __sort_type parameter (e.g., ?__sort_type=test) and observe if the parameter is processed without errorAffected if The application accepts and processes the __sort_type parameter without rejecting or sanitizing the input
-
Inspect database query logs for unsanitized behaviorEnable database query logging if available, then trigger the __sort_type parameter with a value that would produce an error if not properly parameterized (e.g., a quote character). Review logs for unexpected SQL syntax or errorsAffected if The application exhibits SQL errors or unexpected query behavior when special characters are passed through __sort_type, indicating lack of proper input sanitization
You are affected if you are running GoAdmin v1.2.26 with the /admin/info/{table} endpoint exposed and the __sort_type parameter accepts unsanitized input, allowing SQL injection.
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 dataUpgrade to a patched version of GoAdmin that implements proper input sanitization and parameterized queries for the __sort_type parameter; as an interim measure, implement WAF rules to block SQL injection patterns in this parameter.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-51946 — 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-51946 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