CVE-2022-41905

Workarounds

Set dir_browser.enable = False in the configuration. For instance, when using a Python dictionary to configure the library:

config = {
    # your normal configuration
    "dir_browser": {
      "enable": False
    },
}
app = WsgiDAVApp(config)

For more information

Note that an attacker cannot exploit this vulnerability, by simply uploading a file or folder with a manipulated file name.
However if the WsgiDAV library is used in a scenario where untrusted data is displayed in the directory browser's user interface (e.g. 'realm' or user name, ...) XSS may happen.

If you have any questions or comments about this advisory:

• Open an issue in mar10/wsgidav
• See the security policy

Implementations using this library with directory browsing enabled may be susceptible to Cross Site Scripting (XSS) attacks.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2022-41905 has a CVSS score of 8.2 (High). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.1.0); upgrading removes the vulnerable code path.

Kodem intelligence

Users can upgrade to v4.1.0

1. What is CVE-2022-41905? CVE-2022-41905 is a high-severity cross-site scripting (XSS) vulnerability in wsgidav (pip), affecting versions >= 3.0.0a1, < 4.1.0. It is fixed in 4.1.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2022-41905? CVE-2022-41905 has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of wsgidav are affected by CVE-2022-41905? wsgidav (pip) versions >= 3.0.0a1, < 4.1.0 is affected.
4. Is there a fix for CVE-2022-41905? Yes. CVE-2022-41905 is fixed in 4.1.0. Upgrade to this version or later.
5. Is CVE-2022-41905 exploitable, and should I be worried? Whether CVE-2022-41905 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-41905 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-41905? Upgrade wsgidav to 4.1.0 or later.