dbcve.org
Owncloud ServerApplication · Owncloud

CVE-2013-0202

MEDIUM · 6.1 CVSS v3.1 Published 2019-12-17
Fix available
A fix is available. Upgrade to 4.0.11 / 4.5.6 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross-site scripting (XSS) vulnerability in ownCloud 4.5.5, 4.0.10, and earlier allows remote attackers to inject arbitrary web script or HTML via the action parameter to core/ajax/sharing.php.

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 · high confidence

Reflected cross-site scripting (XSS) vulnerability in ownCloud's core/ajax/sharing.php allows remote attackers to inject arbitrary JavaScript or HTML through the unsanitized 'action' parameter. This is a classic input validation failure where user-supplied data is echoed back without proper output encoding.

MitigationUpgrade ownCloud to a version beyond 4.5.5/4.0.10 that includes the patched sharing.php with proper input sanitization and output encoding for the action parameter, or implement WAF rules to block malicious patterns in that parameter.

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
Owncloud ServerApplication
Affected:>= 4.0.0, < 4.0.11>= 4.5.0, < 4.5.6

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
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/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 checks

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

  1. Verify ownCloud installation exists
    Locate the ownCloud installation directory, typically at the web server root (e.g., /var/www/owncloud, /var/www/html/owncloud, or C:\inetpub\wwwroot\owncloud). Confirm the presence of the ownCloud directory structure.
    Affected if ownCloud is not installed on the system.
  2. Determine installed ownCloud version
    Check the version file inside the ownCloud installation directory. In ownCloud 4.x, this is typically a 'version' file in the root ownCloud folder, or access the ownCloud admin interface and navigate to the admin page to view the version number.
    Affected if The installed version falls within 4.0.0 through 4.0.10, or 4.5.0 through 4.5.5.
  3. Locate the vulnerable sharing.php file
    Navigate to the 'core/ajax/' subdirectory within the ownCloud installation folder and confirm the presence of 'sharing.php'. The full path is typically [owncloud_root]/core/ajax/sharing.php.
    Affected if The file core/ajax/sharing.php exists in the ownCloud installation.
  4. Verify sharing functionality is enabled
    Log into the ownCloud admin panel and navigate to the Sharing settings (or check the config/config.php file for 'share_api_enabled' or similar sharing configuration). Alternatively, check if any shares exist in the ownCloud database or file system.
    Affected if The sharing feature is enabled in ownCloud configuration.
  5. Inspect the action parameter handling in sharing.php
    Open core/ajax/sharing.php in a text editor and search for the section where the 'action' parameter is processed. Look for whether the parameter value is echoed back without htmlspecialchars() or equivalent encoding. Unpatched versions will show the action parameter being used directly in output.
    Affected if The 'action' parameter is used in output statements without proper sanitization functions like htmlspecialchars(), htmlentities(), or similar encoding.

A user is affected if ownCloud versions 4.0.0-4.0.10 or 4.5.0-4.5.5 are installed, the core/ajax/sharing.php file exists, sharing is enabled, and the action parameter in sharing.php lacks output encoding.

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.

From vendor data
Upgrade available Upgrade to 4.0.11 / 4.5.6 or later
Fixed in 4.0.114.5.6
Interim mitigation

Upgrade ownCloud to a version beyond 4.5.5/4.0.10 that includes the patched sharing.php with proper input sanitization and output encoding for the action parameter, or implement WAF rules to block malicious patterns in that parameter.

Fix this in Owncloud Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0202 — 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-2013-0202 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