Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-56705 – Unauthenticated Remote Code Execution – Adminer before 5.4.3

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-56705 affects Adminer, the popular single-file PHP database management tool. Versions before 5.4.3 fail to sanitize the server field before it is used to build a PDO DSN string for MSSQL connections, allowing an unauthenticated attacker to inject ODBC parameters and achieve remote code execution. The issue is rated CRITICAL severity.

Technical details

  • Root cause: Adminer builds the MSSQL PDO DSN by directly concatenating user-supplied host/server input (e.g. "sqlsrv:Server=$host") without stripping semicolons, which act as parameter delimiters in ODBC connection strings.
  • Trigger condition: Requires the pdo_sqlsrv PHP extension and the Microsoft ODBC Driver for SQL Server to be installed, and a web-writable directory reachable by the application.
  • Attack vector: An attacker submits a crafted server value (e.g. via the login form) containing semicolon-delimited ODBC parameters such as TraceFile and TraceOn, redirecting the ODBC driver’s connection trace output to a file inside the web root.
  • Impact: Because the trace file can be made to include attacker-controlled connection string content, injecting PHP code into that content and having it written to a web-accessible path results in unauthenticated remote code execution.

Affected software

  • Adminer (all builds) prior to version 5.4.3

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade Adminer to version 5.4.3 or later, which sanitizes the server field before DSN construction.
  • If patching is not immediately possible: Restrict or disable network exposure of the Adminer login page (e.g. place it behind authentication, VPN, or IP allowlisting), and consider removing/disabling the pdo_sqlsrv MSSQL driver support if MSSQL connectivity via Adminer is not required, to eliminate the vulnerable code path.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: Adminer <span class="version">, onclick="bodyClick(event);" onload="verifyVersion(

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge