mar10 wsgidav up to 4.3.4 MySQL mysql_dav_provider.py sql injection

Summaryinfo

A vulnerability marked as critical has been reported in mar10 wsgidav up to 4.3.4. Impacted is the function _exists_record_by_primary_key/_get_field_by_primary_key/_get_record_by_primary_key of the file wsgidav/samples/mysql_dav_provider.py of the component MySQL. This manipulation causes sql injection. This vulnerability is handled as CVE-2026-55509. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability has been found in mar10 wsgidav up to 4.3.4 and classified as critical. Affected by this vulnerability is the function _exists_record_by_primary_key/_get_field_by_primary_key/_get_record_by_primary_key of the file wsgidav/samples/mysql_dav_provider.py of the component MySQL. The manipulation with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

WsgiDAV is a generic and extendable WebDAV server based on WSGI. Prior to 4.3.5, the sample MySQLBrowserProvider in wsgidav/samples/mysql_dav_provider.py concatenates the record key parsed from a request URL directly into SQL WHERE clauses. The affected _exists_record_by_primary_key, _get_field_by_primary_key, and _get_record_by_primary_key methods are part of a shipped example provider that is not enabled by default. An attacker who can access a share explicitly configured with this non-default provider can inject SQL through a normal GET request; anonymously exposed read shares permit a status-code oracle and extraction of arbitrary data reachable by the configured MySQL account. This issue is fixed in version 4.3.5.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-55509 since 06/17/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

Upgrading to version 4.3.5 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• mar10

Name

• wsgidav

Version

• 4.3.0
• 4.3.1
• 4.3.2
• 4.3.3
• 4.3.4

Website

• Product: https://github.com/mar10/wsgidav/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion