dbcve.org
OwncloudApplication

CVE-2015-4716

HIGH · 10.0 CVSS v2.0 Published 2015-10-21
Fix available
A fix is available. Upgrade to after 7.0.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Directory traversal vulnerability in the routing component in ownCloud Server before 7.0.6 and 8.0.x before 8.0.4, when running on Windows, allows remote attackers to reinstall the application or execute arbitrary code via unspecified vectors.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Directory traversal vulnerability in the routing component of ownCloud Server affecting versions before 7.0.6 and 8.0.4 when running on Windows. The vulnerability allows remote attackers to perform path traversal attacks leading to application reinstallation or arbitrary code execution.

MitigationUpgrade ownCloud Server to version 7.0.6 or later, or 8.0.4 or later. This is critical since the vulnerability has a CVSS score of 10 and allows remote code execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OwncloudApplication
Affected:<= 7.0.5
Owncloud ServerApplication
Affected:= 8.0.0= 8.0.2= 8.0.3
WindowsOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify ownCloud Server is installed
    Access the ownCloud web interface or check the server for ownCloud installation directories
    Affected if ownCloud Server is not present on the system
  2. Identify the installed ownCloud version
    Check the ownCloud admin panel for the version number, or examine version.php in the ownCloud root directory
    Affected if The installed version is 7.0.5 or earlier, or is exactly 8.0.0, 8.0.2, or 8.0.3
  3. Confirm the operating system is Windows
    Check the server operating system using systeminfo (Windows) or verify the hosting environment
    Affected if The ownCloud instance is running on any version of Microsoft Windows
  4. Verify the routing component is accessible
    Attempt to access the ownCloud web routing endpoint over HTTP/HTTPS
    Affected if The ownCloud web interface is accessible over the network

A user is affected if ownCloud Server versions 7.0.5 or earlier, or versions 8.0.0, 8.0.2, or 8.0.3 are installed and running on a Windows server with the web interface accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 7.0.5
Interim mitigation

Upgrade ownCloud Server to version 7.0.6 or later, or 8.0.4 or later. This is critical since the vulnerability has a CVSS score of 10 and allows remote code execution.

Recommended fix High confidence

OwnCloud Server 7.0.6 or higher, or 8.0.4 or higher

  1. 1. Back up the ownCloud data directory and database before upgrading
  2. 2. Download OwnCloud Server 7.0.6 or higher (for 7.x branch) OR version 8.0.4 or higher (for 8.0.x branch) from the official ownCloud website
  3. 3. Extract the new version to a temporary location
  4. 4. Stop the ownCloud web server (Apache/Nginx/IIS)
  5. 5. Replace the existing ownCloud files with the new version, preserving the config directory
  6. 6. Update the ownCloud database by running the upgrade command: occ upgrade (or via web updater)
  7. 7. Start the web server
  8. 8. Verify the ownCloud instance is functioning correctly and the version number reflects the upgrade
Caveat Standard upgrade considerations apply - review ownCloud release notes for your specific version jump for any configuration or feature changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Owncloud Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-4716 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-4716 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data