CVE-2013-5059
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 SP2 and 2013, and Office Web Apps 2013, allows remote attackers to execute arbitrary code via crafted page content, aka "SharePoint Page Content Vulnerabilities."
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 is a remote code execution vulnerability in Microsoft SharePoint Server 2010 (SP1/SP2) and 2013, as well as Office Web Apps 2013. Attackers can execute arbitrary code by submitting crafted page content, likely due to insufficient input validation or sanitization of web page parameters.
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= 2013= 2010= 2013CVSS 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.
-
Check SharePoint Server versionOpen SharePoint Management Shell and run: (Get-SPFarm).BuildVersion or Get-SPServer | Select-Object -Property Name, DisplayName, BuildVersionAffected if The build version corresponds to SharePoint Server 2010 or 2013 (including SP1/SP2 for 2010)
-
Check Office Web Apps versionRun the following command on the Office Web Apps server: Get-OfficeWebAppsMachine or check the installed programs in Control Panel for 'Office Web Apps 2013'Affected if Office Web Apps 2013 is installed
-
Identify all SharePoint web applicationsIn SharePoint Management Shell, run: Get-SPWebApplication -IncludeCentralAdministration | Select-Object -Property Name, Url, IsAdministrationWebApplicationAffected if Any web applications are configured and running (the vulnerability is triggered through web page content submission)
-
Check if Claims to Windows Token Service is runningRun: Get-Service -Name 'C2WTS' | Select-Object Name, Status, StartType; This service is commonly associated with SharePoint web service authenticationAffected if The service is running (indicates exposed web services that could be targeted)
-
Verify SharePoint build against known affected versionsCompare your installed build number from step 1 to the affected versions (SharePoint Server 2010 SP1/SP2 and SharePoint Server 2013). The build number can be cross-referenced with Microsoft's version history.Affected if Your SharePoint build matches version 2010 or 2013 and has not been patched beyond the CVE-2013-5059 security update
You are affected if your environment runs SharePoint Server 2010 (any SP1/SP2 build), SharePoint Server 2013, or Office Web Apps 2013, and the security update for CVE-2013-5059 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 Microsoft security update for CVE-2013-5059, or upgrade affected SharePoint installations to a version that includes the patched codebase.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-5059 — 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-5059 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