How severe is CVE-2022-41905?

CVE-2022-41905 has a CVSS score of 8.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-41905?

CVE-2022-41905 affects the following packages: wsgidav (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2022-41905?

Update wsgidav to 4.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-41905 is resolved across your whole dependency graph.

How do I detect CVE-2022-41905 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wsgidav, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-41905 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2022-41905 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-41905 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-41905?

CVE-2022-41905 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 31th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-41905?

CVE-2022-41905 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2022-41905 published, and has it been updated?

CVE-2022-41905 was published on November 11, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

HIGH severity

CVE-2022-41905 — wsgidav

HIGHFix: mar10/wsgidav@e9606ab

CVE-2022-41905 is a high-severity (CVSS 8.2) Cross-site Scripting (XSS) vulnerability in wsgidav. A fix is available for wsgidav — see the affected versions and patch details below.

wsgidav is vulnerable to Cross-Site Scripting (XSS) when directory browsing is enabled

Also known asGHSA-xx6g-jj35-pxjvPYSEC-2022-43018

Published

Nov 11, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-41905.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍wsgidav

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

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

Patches

Users can upgrade to v4.1.0

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`wsgidav`	≥ 3.0.0a1&&< 4.1.0	4.1.0`pip install --upgrade 'wsgidav==4.1.0'`

Affected Products

1 product · 1 configurations

Application

wsgidavwsgidav_project

≥ 3.0.0 && < 4.1.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wsgidav, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update wsgidav to 4.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-41905 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Impact Implementations using this library with directory browsing enabled may be susceptible to [Cross Site Scripting (XSS)](https://owasp.org/www-community/attacks/xss/) attacks. ### Patches Users can upgrade to v4.1.0 ### 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 uploadin