CVE
adminneo-org/adminneo authentication bypass in MS SQL login via empty username
Affects AdminNeo before 5.9.1 using the sqlsrv-based MS SQL driver on Windows, against a SQL Server that accepts the web server's Windows/Kerberos identity. Fixed in 5.9.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 5.9.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 5.9.1.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 36/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
AdminNeo before 5.9.1 contains an authentication bypass vulnerability in the sqlsrv-based MS SQL driver that allows unauthenticated attackers to log in by submitting an empty username. Attackers can supply any non-empty password, triggering Windows integrated authentication that grants a full session with the web server identity's SQL Server privileges.
Who should check
Teams running AdminNeo before 5.9.1 on Windows with the sqlsrv extension against MS SQL Server, such as IIS-hosted sites.
“Affected range: all releases shipping the sqlsrv -based MS SQL driver with this UID /empty-username handling”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach10/20Affects Packagist packages
- Severity9.2/10CVSS 9.2
- No patch0/5No signal
What would change the score
- Would score about 81 if added to CISA KEV
- Would score about 76 if CISA's SSVC rates exploitation active
- Would score about 41 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 5.9.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130380 (AdminNeo before 5.9.1 Authentication Bypass via MS SQL Empty Username), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130380 (entry last updated 2026-11-17):
Affected:
- Packagist package adminneo-org/adminneo: fixed in 5.9.1
Fixed versions: 5.9.1.
Conditions (all must be true for the bug to be hit):
- Runs on Windows with the sqlsrv extension (not PDO_DBLIB or Linux). (source: https://github.com/adminneo-org/adminneo/security/advisories/GHSA-w8j4-8pww-wm83)
- AdminNeo release before 5.9.1 with the sqlsrv-based MS SQL driver. (source: https://github.com/adminneo-org/adminneo/security/advisories/GHSA-w8j4-8pww-wm83)
- The SQL Server must accept the web server's Windows identity. (source: https://github.com/adminneo-org/adminneo/security/advisories/GHSA-w8j4-8pww-wm83)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130380 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130380 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Packagist): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/adminneo-org/adminneo/security/advisories/GHSA-w8j4-8pww-wm83
- https://github.com/adminneo-org/adminneo/releases/tag/v5.9.1
- https://www.vulncheck.com/advisories/adminneo-before-5.9.1-authentication-bypass-via-ms-sql-empty-username
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130380
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130380"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- adminneo-org/adminneoPackagist
fixed in 5.9.1
Evidence 5
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130380
Is CVE-2026-130380 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An unauthenticated visitor can obtain a full AdminNeo session with the web server account's SQL Server privileges. The flaw comes from how the MS SQL driver handles an empty username.Source: github.com
Which versions are affected by CVE-2026-130380?
adminneo-org/adminneo (Packagist): before 5.9.1.Source: cve.now feed data
Am I affected, and how do I check?
AdminNeo releases before 5.9.1 that use the sqlsrv-based MS SQL driver on Windows, where the SQL Server accepts the web server's Windows/Kerberos identity. Check the AdminNeo version and whether the MS SQL driver in use is the sqlsrv one rather than PDO_DBLIB.Source: github.com
How do I fix CVE-2026-130380?
Upgrade AdminNeo to 5.9.1 or later, which is the fixed release listed for this vulnerability.Source: github.com