CVE
adminneo-org/adminneo server-side request forgery in login server field
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/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.
- 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
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.29% · 21st percentile
- 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? →
- 37/100 · provisional
- 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
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
AdminNeo before 5.9.1 contains a server-side request forgery vulnerability that allows unauthenticated attackers to bypass the privileged-port restriction by injecting separator characters or connection-string keywords into the login server field. Attackers can make pgsql, Mongo, Oracle and PDO drivers parse a different host and port, reaching internal services and leaking limited information through driver responses and errors.
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach10/20Affects Packagist packages
- Severity6.9/10CVSS 6.9
- No patch0/5No signal
What would change the score
- Would score about 82 if added to CISA KEV
- Would score about 77 if CISA's SSVC rates exploitation active
- Would score about 42 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-130379 (AdminNeo before 5.9.1 Privileged Port Restriction Bypass via Login Server Field), 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-130379 (entry last updated 2026-11-17):
Affected:
- Packagist package adminneo-org/adminneo: fixed in 5.9.1
Fixed versions: 5.9.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130379 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130379 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-v65x-fj5j-4m4g
- https://github.com/adminneo-org/adminneo/commit/1cd4c894f476614c937dd0285c1ee59774917ebd
- https://github.com/adminneo-org/adminneo/releases/tag/v5.9.1
- https://www.vulncheck.com/advisories/adminneo-before-5.9.1-privileged-port-restriction-bypass-via-login-server-field
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-130379
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-130379"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- adminneo-org/adminneoPackagist
fixed in 5.9.1
Evidence 6
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-130379
Is CVE-2026-130379 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
Which versions are affected by CVE-2026-130379?
adminneo-org/adminneo (Packagist): before 5.9.1.Source: cve.now feed data
How do I fix CVE-2026-130379?
Upgrade to a fixed version: 5.9.1.Source: cve.now feed data