OwncloudApplication
CVE-2013-7344
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/settings.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 issue was SPLIT from CVE-2013-0303 due to different affected versions.
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/settings.php allows remote authenticated users to execute arbitrary PHP code. The vulnerability affects ownCloud versions before 4.0.12 and 4.5.x before 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
= 3.0.0= 3.0.1= 3.0.2= 3.0.3= 4.0.0= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7CVSS 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 versionLocate the version file or admin interface in your ownCloud installation and retrieve the installed version number. This is typically found in a version.php file or displayed in the administrative dashboard.Affected if The installed version is 4.0.11 or earlier, 4.5.x through 4.5.5, or any of 3.0.0, 3.0.1, 3.0.2, 3.0.3, 4.0.0 through 4.0.7.
-
Verify core/settings.php existsCheck for the presence of the file core/settings.php in your ownCloud installation directory. This file is part of the ownCloud core and should exist in a standard ownCloud deployment.Affected if The file core/settings.php exists in your installation.
-
Confirm user authentication is enabledVerify that ownCloud user authentication mechanisms are active. Check if user accounts can log into the ownCloud instance through the web interface or API.Affected if User authentication is enabled and functional, allowing users to log in to the ownCloud instance.
-
Check for unusual PHP executionReview web server access logs and ownCloud logs for unexpected POST requests to core/settings.php or similar endpoints that may indicate exploitation attempts.Affected if Logs show suspicious POST requests to core/settings.php with encoded payloads or PHP code execution patterns.
You are affected if your ownCloud version is 4.0.11 or earlier, 4.5.x through 4.5.5, or versions 3.0.0-3.0.3 and 4.0.0-4.0.7, the core/settings.php file exists, and user authentication is enabled.
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 to version 4.0.12, 4.5.6 or later to resolve the arbitrary PHP code execution vulnerability in core/settings.php.
Fix this in Owncloud
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-7344 — 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-7344 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