OwncloudApplication
CVE-2013-0301
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 request forgery (CSRF) vulnerability in apps/calendar/ajax/settings/settimezone in ownCloud before 4.0.12 allows remote attackers to hijack the authentication of users for requests that change the timezone via the timezone parameter.
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 confidenceCSRF vulnerability in ownCloud's calendar app allows attackers to trick authenticated users into changing their timezone settings. The /apps/calendar/ajax/settings/settimezone endpoint lacks proper request origin validation, enabling cross-site request forgery attacks.
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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/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 installation and versionLocate the ownCloud installation directory and check the version.php or version file. Common paths include /var/www/owncloud, /var/www/html/owncloud, or the web root. Look for a version.php,.version file, or the ownCloud admin panel which displays the version.Affected if The installed version is 4.0.11 or lower, or matches any of these versions: 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, or 4.0.7
-
Verify the calendar app is enabledCheck the ownCloud apps directory for the calendar app presence and status. In the database, check the oc_appconfig table for the calendar app entry, or access the ownCloud admin interface to view enabled apps.Affected if The calendar application is installed and enabled in ownCloud
-
Confirm the vulnerable endpoint existsAccess or probe the URL endpoint /apps/calendar/ajax/settings/settimezone via HTTP request. This can be done with curl or by inspecting the calendar app's AJAX handler files in the ownCloud installation under apps/calendar/ajax/settings/.Affected if The endpoint /apps/calendar/ajax/settings/settimezone is present and accessible without CSRF token validation
You are affected if your ownCloud version is 4.0.11 or lower (or one of the specific versions 3.0.0-3.0.3, 4.0.0-4.0.7) AND the calendar app is enabled, exposing the vulnerable timezone settings endpoint.
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 or later which contains the fix for this vulnerability.
Fix this in Owncloud
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0301 — 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-0301 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