Security incident · CVE-2026-96629
AdminNeo: CSRF Token Secret Recoverable from Single Observed Token, Enabling Cross-Site Request Forgery
Published Oct 30, 2026 · catalog updated Oct 30, 2026 · AdminNeo: CSRF Token Secret
Last checked Nov 7, 2026. A connected source was read within the last 7 days.
Open the advisory
Exploitation likelihood is not on this record for CVE-2026-96629. A missing EPSS score is not a low risk. Compare AdminNeo: CSRF Token Secret with the linked advisory before you change production.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (AdminNeo: CSRF Token Secret).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- EPSS is missing. A missing score is not a low risk.
- Severity
- Medium6.8
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- Not in the current FIRST EPSS dataset
- Remediation
- Advisory link
- Affected products
- Packagist adminneo-org/adminneo · composer adminneo-org
### 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 ( ), 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 lines 1181-1184: Token verification in lines 1189-1192: Session token initialized in lines 327 and 385: **Three distinct weaknesses:** 1. **Instant recovery:** The token format transmits both operands. Recovery is trivial: . 2. **Low entropy**: Only 1,000,000 possible session tokens (~20 bits). Blind brute-force requires at most 1M requests. 3. **Loose comparison**: 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: 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)** The token format is . Both operands are transmitted, so the secret is recovered with a single XOR — zero additional requests needed. **Step 3: Forge unlimited valid CSRF tokens** Each forged token is unique and valid. The attacker can generate as many as needed. **Step 4: Execute arbitrary SQL with the forged token** **Step 5: Verify a random wrong token is rejected (control)** **Weaponized CSRF attack page** In a real attack, the attacker hosts this HTML page an
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Packagist adminneo-org/adminneo0 → 5.5.1
- composer adminneo-orgversion unspecified
How to fix CVE-2026-96629
Upgrade
CVE-2026-96629 lists a fix boundary at 5.5.1. Compare the installed build with that boundary before you change production.
Version check
Fixed in 5.5.1
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
Exploitation likelihood is not on this record for CVE-2026-96629. A missing EPSS score is not a low risk. Compare AdminNeo: CSRF Token Secret with the linked advisory before you change production.
Which versions are affected?
Compare what you have installed with 0 → 5.5.1. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-330: Insufficiently Random Values; CWE-352: Cross-Site Request Forgery (CSRF). EPSS is absent from the current FIRST dataset. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 30, 2026 · GitHub Advisory Database
Detected
### 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
Oct 30, 2026 · GitHub Advisory Database
Fix available
adminneo-org/adminneo fixed in 5.5.1
Oct 30, 2026 · GitHub Advisory Database
Fix available
adminneo-org/adminneo fixed in 5.5.1
Oct 30, 2026 · GitHub Advisory Database
Updated
### 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
Sources
- CVE.orgVulnerability recordCVE-2026-96629
Official CVE identifier
cve.org - GitHub Advisory DatabasePackage advisoryGHSA-wm25-49w3-5qrg
GitHub Advisory Database record mirrored by OSV.
github.com - GitLab Advisory DatabasePackage advisoryCVE-2026-96629
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 on
advisories.gitlab.com - OpenSSF OSV / OSV ScannerPackage advisoryGHSA-wm25-49w3-5qrg
AdminNeo: CSRF Token Secret Recoverable from Single Observed Token, Enabling Cross-Site Request Forgery
osv.dev
References
Freshness
Last verified in this catalog Nov 7, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- GitLab Advisory DatabaseNov 4, 2026
- CVE.orgOct 31, 2026
- GitHub Advisory DatabaseOct 31, 2026
- OpenSSF OSV / OSV ScannerOct 31, 2026