CVE
adminneo-org/adminneo auth bypass in OTP login plugin via permanent cookie
Affects AdminNeo before 5.9.1 deployments that register OtpLoginPlugin with the permanent-login feature. 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:L/AT:N/PR:L/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
- Specific setups only
Do first: Check whether your setup matches what the bug needs. OtpLoginPlugin is registered/enabled in the deployment (precondition for the bypass) Affects AdminNeo versions before 5.9.1 that ship OtpLoginPlugin with the permanent-login feature Attacker must know the primary database password
- 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? →
- 27/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? →
- Specific setups only
- 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 OtpLoginPlugin that allows attackers knowing the database password to skip TOTP verification by abusing the permanent-login cookie. Attackers can submit a login with a wrong OTP and permanent=1 to obtain a neo_permanent cookie, then replay it to gain full authenticated database access.
Who should check
Teams running AdminNeo with OtpLoginPlugin enabled for TOTP two-factor login, including Packagist adminneo-org/adminneo users
“Affects every release shipping OtpLoginPlugin with the permanent-login feature”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects Packagist packages
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 34 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
OtpLoginPlugin is registered/enabled in the deployment (precondition for the bypass) Affects AdminNeo versions before 5.9.1 that ship OtpLoginPlugin with the permanent-login feature Attacker must know the primary database passwordUpgrade 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-130382 (AdminNeo before 5.9.1 TOTP Authentication Bypass via neo_permanent Cookie), 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-130382 (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):
- OtpLoginPlugin is registered/enabled in the deployment (precondition for the bypass) (source: https://github.com/adminneo-org/adminneo/security/advisories/GHSA-xwpg-q47q-pg26)
- Affects AdminNeo versions before 5.9.1 that ship OtpLoginPlugin with the permanent-login feature (source: https://github.com/adminneo-org/adminneo/security/advisories/GHSA-xwpg-q47q-pg26)
- Attacker must know the primary database password (source: https://www.vulncheck.com/advisories/adminneo-before-5.9.1-totp-authentication-bypass-via-neo-permanent-cookie)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130382 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130382 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-xwpg-q47q-pg26
- https://github.com/adminneo-org/adminneo/releases/tag/v5.9.1
- https://www.vulncheck.com/advisories/adminneo-before-5.9.1-totp-authentication-bypass-via-neo-permanent-cookie
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-130382
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-130382"}.Timeline
- CVE published
- First seen 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-130382
Is CVE-2026-130382 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?
The TOTP second factor can be skipped by replaying a permanent-login cookie, so only the database password is needed to gain full authenticated AdminNeo and database access, including read, write and drop.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-130382?
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 ship OtpLoginPlugin with the permanent-login feature are affected, and the plugin must be registered or enabled in the deployment. To check, look at the installed AdminNeo version and whether OtpLoginPlugin is registered in the deployment configuration.Source: github.com, vulncheck.com
How do I fix CVE-2026-130382?
Upgrade AdminNeo to version 5.9.1 or later, which is the fixed version.Source: github.com, vulncheck.com