dbcve.org
Sharepoint FoundationApplication · Microsoft

CVE-2015-1700

MEDIUM · 6.0 CVSS v2.0 Published 2015-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Microsoft SharePoint Server 2007 SP3, SharePoint Foundation 2010 SP2, SharePoint Server 2010 SP2, and SharePoint Foundation 2013 SP1 allow remote authenticated users to execute arbitrary code via crafted page content, aka "Microsoft 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 · high confidence

CVE-2015-1700 is a remote code execution vulnerability in Microsoft SharePoint Server 2007 SP3, 2010 SP2, and SharePoint Foundation 2013 SP1. The flaw allows authenticated remote users to execute arbitrary code through crafted page content, likely due to insufficient sanitization of user-supplied content in SharePoint pages.

MitigationApply the appropriate Microsoft security updates for the affected SharePoint versions, or upgrade to supported SharePoint versions that are no longer vulnerable. Verify that authentication mechanisms and page rendering still function correctly after patching.

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
Sharepoint FoundationApplication
Affected:= 2010
Sharepoint ServerApplication
Affected:= 2007= 2010= 2013

CVSS 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
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify SharePoint version
    Open SharePoint Central Administration, go to System Settings > Manage servers in this farm, or run Get-SPFarm | Select-Object BuildVersion in SharePoint Management Shell
    Affected if The version shown is 2007, 2010, or 2013 (specifically any 2007, 2010, or 2013 installation regardless of SP level)
  2. Confirm exact build number
    In SharePoint Management Shell, run (Get-SPFarm).BuildVersion to get the full version string such as 14.0.7153.5000 for SharePoint 2010 or 15.0.4719.5000 for SharePoint 2013
    Affected if The major version is 12 (2007), 14 (2010), or 15 (2013)
  3. Check SharePoint edition type
    In Central Administration, go to Upgrade and Migration > Check product and patch installation status, or run Get-SPProduct -Server $env:COMPUTERNAME | Select-Object -ExpandProperty Versions
    Affected if The product is SharePoint Server or SharePoint Foundation versions 2007, 2010, or 2013
  4. Verify authentication configuration
    In Central Administration, go to Application Management > Manage web applications > Authentication Providers, or check if the web application allows NTLM, Kerberos, or forms-based authentication
    Affected if Any form of user authentication is enabled, as the vulnerability is exploited by authenticated users
  5. Confirm user content features are active
    Check if SharePoint sites have publishing features enabled or allow users to create/edit pages. Go to Site Settings > Site Collection Features or Site Features in any affected web application
    Affected if Publishing features or user page creation is enabled, allowing user-supplied content to be rendered

Your environment is affected if you are running SharePoint Server or Foundation versions 2007, 2010, or 2013 with any form of user authentication enabled and user content rendering capabilities active.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate Microsoft security updates for the affected SharePoint versions, or upgrade to supported SharePoint versions that are no longer vulnerable. Verify that authentication mechanisms and page rendering still function correctly after patching.

Fix this in Sharepoint Foundation Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-1700 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-1700 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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