How severe is CVE-2013-1939?

No CVSS score has been assigned to CVE-2013-1939 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-1939?

CVE-2013-1939 affects the following packages: sabre/dav (Packagist), sabre/dav (Packagist), sabre/dav (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2013-1939?

Update sabre/dav to 1.7.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-1939 is resolved across your whole dependency graph.

How do I detect CVE-2013-1939 in my Packagist dependencies?

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

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2013-1939 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-1939 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-2013-1939?

CVE-2013-1939 has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 78th 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-2013-1939?

CVE-2013-1939 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-1939 published, and has it been updated?

CVE-2013-1939 was published on May 14, 2022 and was last updated on December 4, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2013-1939 — dav

CVE-2013-1939 is a Improper Input Validation vulnerability in sabre/dav. A fix is available for sabre/dav — see the affected versions and patch details below.

SabreDAV Directory Traversal vulnerability

Published

May 14, 2022

Updated

Dec 4, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs78th percentile — riskier than 78% of all scored CVEsHighest risk

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

Real-World Exposure

3 pkgs affected

🐘sabre/dav🐘sabre/dav🐘sabre/dav

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

Description

The HTML\Browser plugin in SabreDAV before 1.6.9, 1.7.x before 1.7.7, and 1.8.x before 1.8.5, as used in ownCloud, when running on Windows, does not properly check path separators in the base path, which allows remote attackers to read arbitrary files via a \ (backslash) character.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`sabre/dav`	≥ 1.7.0&&< 1.7.7	1.7.7`composer require sabre/dav:^1.7.7`
🐘Packagist	`sabre/dav`	≥ 1.8.0&&< 1.8.5	1.8.5`composer require sabre/dav:^1.8.5`
🐘Packagist	`sabre/dav`	≥ 1.6.0&&< 1.6.9	1.6.9`composer require sabre/dav:^1.6.9`

Affected Products

2 products · 6 configurations

Application

sabredavfruux

≥ 1.8.0 && < 1.8.5

range

Application

owncloud serverowncloud

≥ 5.0.0 && < 5.0.4

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sabre/dav, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update sabre/dav to 1.7.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-1939 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.