CVE-2016-0011
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 2013 SP1 and SharePoint Foundation 2013 SP1 allow remote authenticated users to bypass intended Access Control Policy restrictions and conduct cross-site scripting (XSS) attacks by modifying a webpart, aka "Microsoft SharePoint Security Feature Bypass," a different vulnerability than CVE-2015-6117.
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 security feature bypass vulnerability in Microsoft SharePoint Server 2013 SP1 and SharePoint Foundation 2013 SP1 that allows authenticated remote users to bypass intended Access Control Policy restrictions and conduct cross-site scripting (XSS) attacks by modifying a webpart.
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= 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
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 the installed SharePoint versionOpen SharePoint Management Shell and run: Get-SPFarm | Select-Object BuildVersion, Version. Alternatively, check Programs and Features in Control Panel for Microsoft SharePoint Server 2013 or Microsoft SharePoint Foundation 2013.Affected if The installed version is Microsoft SharePoint Server 2013 or Microsoft SharePoint Foundation 2013 (any build)
-
Determine if lower-privileged users can modify webpartsIn SharePoint Central Administration, go to Application Management > Manage web applications > User Policy. Check if users with limited permissions (such as Contribute or Edit level) have permissions to modify or add webparts on any site collection.Affected if Users with permissions below Full Control or Design can add, edit, or modify web parts on affected sites
-
Review Access Control Policy settings for webpart pagesNavigate to Site Settings > Site Permissions for each affected site collection. Verify the permission levels assigned to user groups, specifically checking if the "Open" or "View" permissions are being overridden by custom webpart policies.Affected if Custom Access Control Policies exist that allow authenticated users to modify webpart content without proper restriction
-
Audit existing webparts for potential XSS contentUsing SharePoint Designer or PowerShell (Get-SPOWebPart -PageUrl), enumerate all webparts on pages accessible to lower-privileged users. Inspect the webpart content for unsanitized user input that could contain script tags or HTML attributes.Affected if Webparts contain unsanitized content that could be exploited for cross-site scripting
A user is affected if they are running SharePoint 2013 and lower-privileged authenticated users have the ability to modify or add web parts on any site collection.
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-2016-0011; in the interim, restrict or disable the ability for lower-privileged users to modify webparts and implement additional input validation on webpart content.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0011 — 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-2016-0011 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