CVE-2013-3895
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 2007 SP3 and 2010 SP1 and SP2 allows remote attackers to conduct clickjacking attacks via a crafted web page, aka "Parameter Injection 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 confidenceThis is a clickjacking vulnerability in Microsoft SharePoint Server 2007 SP3 and 2010 SP1/SP2. Attackers can embed SharePoint pages within invisible iframes on malicious websites, tricking users into clicking unintended actions (parameter injection). The vulnerability stems from the server not properly validating or restricting frame embedding of its content.
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= 2007= 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.
-
Identify installed SharePoint versionOpen SharePoint Central Administration > Help > About Microsoft SharePoint Products, or run PowerShell: (Get-SPFarm).BuildVersion.ToString()Affected if Version is 2007 (any build), 2010 (any build), or 2013 (any build) and falls within the affected ranges listed in the CVE advisory
-
Check if X-Frame-Options header is present on SharePoint sitesUsing a browser, open Developer Tools (F12), go to the Network tab, and load a SharePoint page. Check response headers for 'X-Frame-Options'. Alternatively, run: Invoke-WebRequest -Uri 'https://your-sharepoint-site.com' -Method Head | Select-Object -ExpandProperty HeadersAffected if The X-Frame-Options header is missing, not set to 'DENY' or 'SAMEORIGIN', or the header is not present in the HTTP response
-
Verify if SharePoint pages can be embedded in iframesCreate a test HTML page with an iframe pointing to a SharePoint page (e.g., <iframe src='https://your-sharepoint-site.com/Pages/default.aspx'></iframe>) and open it in a browser. Check if the content renders successfully.Affected if The SharePoint page loads inside the iframe without being blocked, indicating the server does not restrict frame embedding
Your environment is affected if you run any of the listed SharePoint versions AND the X-Frame-Options header is missing or not properly set, allowing your SharePoint pages to be embedded in iframes on external sites.
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 Microsoft security patches for CVE-2013-3895 and configure X-Frame-Options header to 'DENY' or 'SAMEORIGIN' on SharePoint web applications to prevent unauthorized iframe embedding.
- 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-2013-3895 — 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-3895 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