OwncloudApplication
CVE-2013-0303
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 · uneditedUnspecified vulnerability in core/ajax/translations.php in ownCloud before 4.0.12 and 4.5.x before 4.5.6 allows remote authenticated users to execute arbitrary PHP code via unknown vectors. NOTE: this entry has been SPLIT due to different affected versions. The core/settings.php issue is covered by CVE-2013-7344.
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 confidenceAuthenticated remote code execution vulnerability in ownCloud's core/ajax/translations.php allowing remote authenticated users to execute arbitrary PHP code. The vulnerability affects ownCloud versions prior to 4.0.12 and 4.5.x prior to 4.5.6.
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
<= 4.0.11
Owncloud ServerApplication
= 4.0.0= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 4.0.8= 4.0.9= 4.0.10= 4.5.0CVSS 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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/A:P
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.
-
Identify ownCloud versionCheck the ownCloud version by accessing the ownCloud admin panel, or by inspecting the version.php file in the ownCloud root directory (e.g., /var/www/owncloud/version.php or similar). Look for a variable containing the version number.Affected if The installed version is 4.0.11 or lower, or exactly 4.5.0.
-
Locate translations.php endpointVerify the existence of the file core/ajax/translations.php in the ownCloud web root. Check if the file is accessible via HTTP/HTTPS by navigating to your_owncloud_url/core/ajax/translations.php.Affected if The file exists and is web-accessible.
-
Confirm PHP execution capabilityThe vulnerability allows arbitrary PHP code execution through the translations.php endpoint. This is a pre-authentication requirement - an attacker would need valid credentials to exploit this flaw.Affected if The translations.php endpoint accepts and executes PHP code passed through request parameters, and the server has an active user account that could be compromised.
-
Check web server accessibilityDetermine if the ownCloud server is network-accessible. This is a remote vulnerability, so the server must be reachable over the network for an external attacker to exploit it.Affected if The ownCloud server is exposed to untrusted networks or the internet.
A user is affected if their ownCloud installation is version 4.0.11 or lower, or exactly version 4.5.0, the translations.php file exists and is accessible, and the server accepts remote authenticated connections.
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 to ownCloud 4.0.12 or 4.5.6 or later; if upgrade is not feasible, restrict access to the translations.php endpoint to trusted authenticated users only via web server configuration.
Fix this in Owncloud
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2013-0303 — 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-2013-0303 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