AdminNeo SQLite Database-List Drop Arbitrary File Deletion

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary AdminNeo allows an authenticated SQLite-mode user to delete arbitrary files writable by the PHP process through the database-list drop action. The SQLite driver validates file extensions when creating or renaming databases, but the database-list drop path passes submitted `db[]` values directly to `unlink()`. Originally reported by @slpoiuewalspoid-dotcom in Adminer: https://github.com/vrana/adminer/security/advisories/GHSA-6pg3-chwq-wgqc

Impact An authenticated AdminNeo SQLite user with a valid CSRF token can submit an arbitrary relative file path in the database-list `db[]` field. If the PHP process can delete that path, AdminNeo unlinks it even when the file is not a SQLite database.

Root Cause The database-list page accepts selected database names from the POST body and calls `drop_databases()`: ```php if ($_POST["db"]) { queries_redirect(substr(ME, 0, -1), lang('Databases have been dropped.'), drop_databases($_POST["db"])); } ``` In SQLite mode,…

Published by the source

30 Oct 2026, 22:52 UTC

Last modified by the source

30 Oct 2026, 23:00 UTC

Source last checked

31 Oct 2026, 06:45 UTC

1. Revision 2 · amended · 31 Oct 2026

   Amended from osv record GHSA-6vfx-w7q3-42gq

2. Revision 1 · created · 30 Oct 2026

   Published from ghsa record GHSA-6vfx-w7q3-42gq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-96633

Advisory: AdminNeo SQLite Database-List Drop Arbitrary File Deletion
IDs: CVE-2026-96633, GHSA-6vfx-w7q3-42gq
Record: https://patchnext.com/advisories/cve-2026-96633 (revision 2, source checked 31 Oct 2026, 06:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: adminneo-org/adminneo 5.5.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist adminneo-org/adminneo: affected < 5.5.1; fixed in 5.5.1

## Suggested inspection (read-only)
- Packagist adminneo-org/adminneo: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on adminneo-org/adminneo.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6vfx-w7q3-42gq (GitHub-reviewed advisory GHSA-6vfx-w7q3-42gq lists affected ranges: Packagist adminneo-org/adminneo >=0 <5.5.1)
- Verified: https://osv.dev/vulnerability/GHSA-6vfx-w7q3-42gq (OSV record GHSA-6vfx-w7q3-42gq lists affected ranges: Packagist adminneo-org/adminneo >=0 <5.5.1 (fixed))

Commands are suggestions: review each one before running it.