CVE-2013-0080
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 · uneditedMicrosoft SharePoint Server 2010 SP1 and SharePoint Foundation 2010 SP1 allow remote attackers to bypass intended read restrictions for content, and hijack user accounts, via a crafted URL, aka "Callback Function Vulnerability."
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 · moderate confidenceThis vulnerability in Microsoft SharePoint Server 2010 SP1 and SharePoint Foundation 2010 SP1 allows remote attackers to bypass intended read restrictions on content through a specially crafted URL. The flaw, located in a callback function, enables attackers to hijack user accounts by tricking authenticated users into visiting malicious URLs.
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= 2010= 2010CVSS 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
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/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 SharePoint versionOpen SharePoint Central Administration > System Settings > Manage server in this farm. Check the Configuration database version, or run Get-SPFarm | Select BuildVersion in SharePoint Management Shell.Affected if The version shows SharePoint Foundation or Server 2010 (build number 14.x) without the CVE fix applied.
-
Confirm Service Pack 1 is installedIn SharePoint Central Administration > System Settings > Manage server in this farm, view the Configuration database version. SP1 corresponds to specific build numbers. Alternatively, run Get-SPProductVersions in PowerShell.Affected if SharePoint 2010 with SP1 is installed and the security update for CVE-2013-0080 has not been applied.
-
Review SharePoint callback request logsExamine IIS logs (typically in C:\inetpub\logs\LogFiles\W3SVC*) for unusual or suspicious callback URL patterns, especially involving the /_layouts/ directory or forms-based authentication callbacks.Affected if Unusual callback URLs are observed that suggest unauthorized access attempts to restricted content.
-
Check for access control bypass indicatorsReview SharePoint audit logs (Site Collection Administration > Audit Log) for access events to documents or lists where users accessed content they should not have permission to read based on their permissions.Affected if Evidence exists of users accessing content outside their expected permission boundaries through specially crafted URLs.
Your environment is affected if you are running SharePoint Server or Foundation 2010 with SP1 installed and the CVE-2013-0080 security update has not been applied.
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 dataApply the relevant Microsoft security update for CVE-2013-0080 from the Microsoft Security Bulletin. Until patched, restrict access to SharePoint sites via network-level controls and monitor for suspicious callback requests.
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0080 — 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-0080 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