OwncloudApplication
CVE-2016-1498
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 · uneditedCross-site scripting (XSS) vulnerability in the OCS discovery provider component in ownCloud Server before 7.0.12, 8.0.x before 8.0.10, 8.1.x before 8.1.5, and 8.2.x before 8.2.2 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors involving a URL.
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 confidenceCross-site scripting (XSS) vulnerability in the OCS discovery provider component of ownCloud Server allows remote attackers to inject arbitrary web script or HTML via unspecified vectors involving a URL. The vulnerability affects versions 7.0.x before 7.0.12, 8.0.x before 8.0.10, 8.1.x before 8.1.5, and 8.2.x before 8.2.2.
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
<= 7.0.11= 8.2.0= 8.2.1
Owncloud ServerApplication
= 8.0.0= 8.0.2= 8.0.3= 8.0.4= 8.0.5= 8.0.6= 8.0.8= 8.0.9= 8.1.0= 8.1.1= 8.1.3= 8.1.4CVSS 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
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Determine ownCloud Server versionCheck the version.php file in the ownCloud installation directory, typically located at /var/www/html/owncloud/version.php, or access the OCS API endpoint /ocs/v1.php?service=capabilities to retrieve version information via a web request.Affected if The installed version falls within 7.0.0-7.0.11, 8.0.0-8.0.9, 8.1.0-8.1.4, or 8.2.0-8.2.1.
-
Verify OCS discovery provider is accessibleAttempt to access the OCS discovery endpoint, typically at /ocs/v1.php?service=discovery or similar OCS service URLs. This can be done via curl or a browser request to the ownCloud server.Affected if The OCS discovery endpoint responds and returns data, indicating the component is active.
-
Inspect OCS API response for URL parametersReview the raw HTTP response from the OCS discovery endpoint and examine whether URL-based parameters or user-controllable data appear in the response without sanitization. Look for any reflected URL parameters in the JSON or XML output.Affected if URL parameters or unsanitized input from the request are reflected directly in the OCS discovery response without encoding.
You are affected if your ownCloud Server version is 7.0.x before 7.0.12, 8.0.x before 8.0.10, 8.1.x before 8.1.5, or 8.2.x before 8.2.2 AND the OCS discovery provider component is accessible and returns unsanitized URL-based input in its responses.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade ownCloud Server to version 7.0.12, 8.0.10, 8.1.5, or 8.2.2 or later. Alternatively, implement input validation and output encoding on the OCS discovery provider component to sanitize URL-based user input before rendering.
Fix this in Owncloud
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1498 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-1498 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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