dbcve.org
Office Web Apps ServerApplication · Microsoft

CVE-2014-0251

HIGH · 9.0 CVSS v2.0 Published 2014-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
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 Windows SharePoint Services 3.0 SP3; SharePoint Server 2007 SP3, 2010 SP1 and SP2, and 2013 Gold and SP1; SharePoint Foundation 2010 SP1 and SP2 and 2013 Gold and SP1; Project Server 2010 SP1 and SP2 and 2013 Gold and SP1; Web Applications 2010 SP1 and SP2; Office Web Apps Server 2013 Gold and SP1; SharePoint Server 2013 Client Components SDK; and SharePoint Designer 2007 SP3, 2010 SP1 and SP2, and 2013 Gold and SP1 allow remote authenticated users to execute arbitrary code via crafted page content, aka "SharePoint Page Content 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 · high confidence

A remote code execution vulnerability in Microsoft SharePoint allows authenticated users to execute arbitrary code through crafted page content. The vulnerability stems from improper handling of page content within SharePoint's content management system, enabling users with standard authenticated access to inject and execute malicious code.

MitigationApply Microsoft security patches for CVE-2014-0251 to all affected SharePoint products. Until patches are applied, limit SharePoint user permissions to minimum required and monitor for suspicious page content modifications.

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
Office Web Apps ServerApplication
Affected:= 2013
Project ServerApplication
Affected:= 2010= 2013
Sharepoint DesignerApplication
Affected:= 2007= 2010= 2013
Sharepoint FoundationApplication
Affected:= 2010= 2013
Sharepoint ServerApplication
Affected:= 2007= 2010= 2013
Sharepoint Server Client Components SdkApplication
Affected:= 2013
Sharepoint ServicesApplication
Affected:= 3.0
Web ApplicationsApplication
Affected:= 2010

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
Low
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/C:C/I:C/A:C

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 installed SharePoint product and version
    Open SharePoint Management Shell and run: Get-SPFarm | Select-Object BuildVersion, Version, Products. Alternatively, check Programs and Features for Microsoft SharePoint entries to identify the specific product and installed version.
    Affected if The installed product matches one of the affected products (Office Web Apps Server 2013, Project Server 2010/2013, SharePoint Designer 2007/2010/2013, SharePoint Foundation 2010/2013, SharePoint Server 2007/2010/2013, SharePoint Server Client Components SDK 2013, SharePoint Services 3.0, Web Applica
  2. Verify user permissions on SharePoint sites
    Using SharePoint Management Shell, run: Get-SPSite -WebApplication "URL" | Get-SPWeb | Get-SPUser -Web $_ | Select-Object Name, Roles to enumerate users with contributor or higher permissions. Alternatively, check site permissions through Central Administration > Application Management > User Permissions.
    Affected if The site contains authenticated users with Add, Edit, or Full Control permissions, as these roles can modify page content where the vulnerability is exploited.
  3. Inspect page content for unexpected script or web part injections
    Navigate to Site Settings > Site Content and Structure or use SharePoint Designer to view all pages. Check aspx pages in the Pages library for suspicious script tags, encoded content, or unauthorized custom web parts.
    Affected if Pages contain unexpected JavaScript, VBScript, or custom web parts that were not authored by administrators, indicating possible exploitation.
  4. Review SharePoint audit logs for page modifications
    In Central Administration, go to Monitoring > Review job definitions and verify the Audit Log Trimming job runs. Access logs via Site Settings > Site Collection Administration > Audit Log Reports and review 'Content Modification' reports.
    Affected if Audit logs show page content modifications by standard users that include script injection patterns or unusual code execution requests.

You are affected if you run any of the listed SharePoint products matching the affected versions AND have authenticated users with page edit permissions, as the vulnerability allows code execution through crafted page content.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security patches for CVE-2014-0251 to all affected SharePoint products. Until patches are applied, limit SharePoint user permissions to minimum required and monitor for suspicious page content modifications.

Recommended fix High confidence

Upgrade to SharePoint Server 2013 with SP1 or later, or migrate to newer versions as SharePoint 2007 and 2010 have reached end of support

  1. Locate the Microsoft Security Bulletin MS14-022 which addresses this vulnerability
  2. Apply the appropriate patch for your specific SharePoint product and version from MS14-022
  3. For SharePoint Server 2007 SP3: Apply KB2838072
  4. For SharePoint Server 2010 SP1/SP2: Apply KB2838073
  5. For SharePoint Server 2013 Gold/SP1: Apply KB2838075
  6. For SharePoint Foundation 2010 SP1/SP2: Apply KB2838073
  7. For SharePoint Foundation 2013 Gold/SP1: Apply KB2838075
  8. For Project Server 2010 SP1/SP2: Apply KB2838073
Caveat Patches may require downtime for deployment and testing; ensure backup before applying; SharePoint 2007 has reached end of support so continued use carries additional risk

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Office Web Apps Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-0251 — 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-2014-0251 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