Owncloud ServerApplication · Owncloud
CVE-2013-1850
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 · uneditedMultiple incomplete blacklist vulnerabilities in (1) import.php and (2) ajax/uploadimport.php in apps/contacts/ in ownCloud before 4.0.13 and 4.5.x before 4.5.8 allow remote authenticated users to execute arbitrary PHP code by uploading a .htaccess file.
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 confidenceThis is a file upload vulnerability in ownCloud's contacts application where the code uses an incomplete blacklist to restrict uploaded file types. Authenticated users can upload a .htaccess file, which Apache processes to enable arbitrary PHP code execution on the server.
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
= 4.5.0= 4.5.1= 4.5.2= 4.5.3= 4.5.4= 4.5.5= 4.5.6= 4.5.7= 3.0.0= 3.0.1= 3.0.2= 3.0.3
OwncloudApplication
<= 4.0.12CVSS 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 installed ownCloud versionAccess the ownCloud admin settings page to view the version number, or locate the version.php file in the ownCloud root installation directory and read the version constantAffected if The installed version is 4.5.0, 4.5.1, 4.5.2, 4.5.3, 4.5.4, 4.5.5, 4.5.6, 4.5.7, 3.0.0, 3.0.1, 3.0.2, 3.0.3 or is less than or equal to 4.0.12
-
Verify contacts application is enabledLog into the ownCloud web interface as an administrator, navigate to the Apps section, and check if the Contacts application is installed and enabledAffected if The Contacts app is enabled and the ownCloud version falls within the affected ranges listed above
-
Confirm web server allows .htaccess processingExamine the Apache configuration file (httpd.conf or the virtual host configuration) for the ownCloud web directory and verify the AllowOverride directive. Also check if .htaccess files are being readAffected if AllowOverride is set to All or a value that permits .htaccess processing, rather than None
-
Look for unauthorized .htaccess files in user storageSearch the ownCloud data directory, particularly within user files and the contacts app storage area, for any .htaccess files that were not placed there by the administratorAffected if Any .htaccess files exist in user-writable directories under the ownCloud data folder
The environment is affected if the ownCloud version is one of the affected versions (4.5.0-4.5.7, 3.0.0-3.0.3, or <=4.0.12), the Contacts application is enabled, and the web server is configured to process .htaccess files.
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.13 or 4.5.8 or later, and implement allowlist-based file type validation with explicit blocking of .htaccess and other potentially dangerous file extensions.
Fix this in Owncloud Server
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1850 — 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-1850 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