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

Back
New CVE Detected

CVE-2026-55509 – Blind SQL Injection – WsgiDAV MySQLBrowserProvider ≤ 4.3.4

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-55509 is a blind SQL injection vulnerability in the sample MySQLBrowserProvider shipped with WsgiDAV, a WSGI-based WebDAV server. Versions prior to 4.3.5 concatenate a URL-derived record key directly into SQL WHERE clauses without sanitization, allowing an unauthenticated attacker to extract data from the backing MySQL database. The issue is rated HIGH severity (8.8) but only affects deployments that have explicitly enabled this non-default sample provider.

Technical details

  • Root cause: The _exists_record_by_primary_key, _get_field_by_primary_key, and _get_record_by_primary_key methods in the sample MySQL DAV provider build SQL queries by directly concatenating a record key parsed from the request URL, with no escaping or parameterization.
  • Trigger conditions: The vulnerable provider must be explicitly configured and enabled as the DAV backend; it is not active in a default WsgiDAV installation.
  • Attack vector: Network-based, unauthenticated. A crafted path such as /db/users/0' OR '1'='1 injected into a standard WebDAV GET request manipulates the underlying SQL query.
  • Impact: The application returns different HTTP status codes (e.g., 500 vs. 404) depending on whether the injected condition is true, creating a status-code oracle. This allows attackers to extract arbitrary data reachable by the configured MySQL account, and potentially modify data if that account has write privileges.

Affected software

  • WsgiDAV versions prior to 4.3.5, specifically deployments that have enabled the sample mysql_dav_provider (MySQLBrowserProvider) module.
  • Fixed in WsgiDAV 4.3.5 (released 2026-06-27).

Severity

CVSS v4.0 Base Score: 8.8 (High)
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade WsgiDAV to version 4.3.5 or later.
  • If patching is not immediately possible: Disable or remove the MySQLBrowserProvider sample module from the WsgiDAV configuration if it has been enabled; restrict network access to any WsgiDAV instance exposing this provider; audit MySQL account permissions used by the provider to limit data exposure and prevent write access.

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.

  • Rendered/raw response body: a link to https://github.com/mar10/wsgidav/ followed by text reading WsgiDAV/<version>
  • The generator meta tag’s content: WsgiDAV/<version>
  • Page title: text beginning with WsgiDAV - Index of

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