SQL Injection in WsgiDAV (CVE-2026-55509)
Summary
SQL injection in WsgiDAV (CVE-2026-55509). Risk of unauthorized operations or information disclosure. Exploitable via MySQLBrowserProvider. Mitigation: upgrade to 4.3.5 or later.
Original description
The description as published by the source.
Summary
The sample MySQLBrowserProvider builds its SQL queries by concatenating strings, and the record key from the request URL goes straight into the WHERE clause with no escaping. Any user who can reach a share backed by this provider can inject SQL through the URL. Since these read shares are commonly published without authentication, an anonymous attacker can read arbitrary data from the backing database. Confirmed locally with a boolean oracle and full data extraction.
Note:
The MySQLBrowserProvider module is only provided as an example for WsgiDAV and not enabled by default.
Installations that do not explicitly activate the module in their configuration are not affected by this vulnerability.
Details
A path like /db/users/1 is split into a table name and a key. The table name is validated against the real table list, but the key is dropped directly into the query. For the configured table the resulting statement is SELECT id FROM testdb.users WHERE id = '', so a single quote in the key breaks out of the literal and the rest runs as SQL.
The provider's numeric-type check has a typo (INTT instead of INT), so even integer primary keys take the quoted branch, but that branch is equally injectable, just with a quote breakout. The injectable key is read during the normal existence check on a plain GET, so no authentication, write access, or special method is needed.
The behavior shows up cleanly as a status-code oracle. A condition that matches…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55509 has been found in WsgiDAV.
Attackers can target a specific entry point like MySQLBrowserProvider over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade WsgiDAV to 4.3.5 or later.
If unsure, ask your IT team or search "WsgiDAV CVE-2026-55509" on the vendor's site.
CVE-2026-55509 (WsgiDAV) — CWE-89
Attack surface: MySQLBrowserProvider / INTT / INT / dump.py
Patched: 4.3.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in WsgiDAV. Attackers reach the vulnerable code path via MySQLBrowserProvider.
Check the vendor advisory for the affected versions of WsgiDAV. Attack surface: MySQLBrowserProvider / INTT / INT / dump.py.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.3.5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'WsgiDAV' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'WsgiDAV' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
WsgiDAVを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade WsgiDAV to 4.3.5ステージング環境で 4.3.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。