Skip to content
Fencer Intel
medium 5.0

CVE-2013-1939 json

SabreDAV Directory Traversal vulnerability

published 12y ago modified 4mo ago also GHSA-qg5v-jw6f-rpfj , EUVD-2022-4965

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.8%
EPSS 1.8% chance of exploitation in 30 days, percentile 78%
public exploits
0
none known

Summary

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.

Patch / fix

  • packagist sabre/dav 1.6.9, 1.7.7, 1.8.5
  • fruux sabredav 1.6.9, 1.7.7, 1.8.5
  • owncloud owncloud_server 4.0.14, 4.5.9, 5.0.4

Is CVE-2013-1939 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-1939 updated cvss 5.0

php-sabredav-Sabre_DAV: Local file exposure due improper icons / images path checking in the HTML Browser plug-in

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.78% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

Affected packages

ecosystem package affected fixed in
packagist sabre/dav
>=1.7.0, <1.7.7
>=1.8.0, <1.8.5
>=1.6.0, <1.6.9
1.7.7
1.8.5
1.6.9

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.