Microsoft sharepoint enterprise server 2016, code injection: 7 records, one defect family
Microsoft sharepoint enterprise server 2016 has been reported 7 separate times for the same kind of mistake, CWE-94, between 2021-05-11 and 2026-08-11. A defect family is our own grouping of the CVE corpus: every record naming one product and one weakness class, collected so a repeat is visible as a repeat. No public source publishes this, and what this page counts is how often this one product has gone wrong in this one way.
What this page is, and what it is not
The records are public. This grouping is not. No source publishes defect families, so we built them: every record in the corpus sorted by the product an authority named and the weakness class carried with it, 21316 families over 105586 records. This one holds every record that names Microsoft sharepoint enterprise server 2016 and carries CWE-94, matched character for character. We show the join because a grouping you cannot check is a grouping you should not cite.
One record is an incident. 7 filings, between 2021-05-11 and 2026-08-11, all landing on the same weakness class in the same product, is a habit in what gets reported here, and a habit is something you can plan around. This is what we held on 2026-09-20.
A repeat is evidence about where to look. If you are reviewing Microsoft sharepoint enterprise server 2016, the records below say which mistake has already been found more than once, which is the cheapest place a reviewer can start. If you are asking the vendor a question, a count under one weakness class is a better question than any single record is.
What this page cannot tell you is decided by what was joined. A product name and a weakness class settled membership, so those two values are the whole of what the page asserts. Records here may sit in the same line of code or in unrelated parts of the product, and we hold no value that separates those cases. A fixed version named in one record closes that record and says nothing about the others. And nothing here describes anyone's systems, because no value in this family connects a product name to an installation.
The names the authorities used
One spelling, used by every authority that filed one of these records: microsoft sharepoint enterprise server 2016.
Family membership: held values. Joined on the product and weakness class the assigning authorities wrote, with no model involved.
What the records offer
All 7 records publish a fixed version.
2 records are listed by CISA with a required action, which carries a federal remediation deadline on its own page.
The earliest was published 2021-05-11 and the latest 2026-08-11. That span is how long this product kept producing this weakness, not how long any one record took to fix.
What this family was researched, not held
SharePoint code injection: found at Pwn2Own, then used in attacks
These records all describe code injection in Microsoft SharePoint Server, and they run from 2021 to 2026. Two of them reached CISA's exploited catalog after first appearing in a hacking contest. CVE-2023-24955 was shown at Pwn2Own Vancouver in March 2023 as half of a chain with CVE-2023-29357, and CISA added it on 26 March 2024 with a 16 April deadline. CVE-2025-49704 came out of the ToolShell chain demonstrated at Pwn2Own Berlin on 17 May 2025, was published by Microsoft on 8 July 2025, was seen in attacks by 17 July, and was added by CISA on 22 July. Microsoft then published CVE-2025-53770 on 19 July 2025 and said its update carried more robust protections than the update for CVE-2025-49704, so the first repair was revisited within days.
Contest research on this product has repeatedly turned into real attacks, and the gap has been months rather than years. If you run SharePoint Server on your own hardware, check each of these records against your build on its own, and pay attention to the ones where Microsoft later shipped a second, stronger update.
This note says only that these records read alike: one product line, one weakness class. It does not say they share a vulnerability, share an estate, or that applying one fix addresses any of the others.
Written from securityweek.com, unit42.paloaltonetworks.com, cisa.gov, cveawg.mitre.org. Stated at high confidence. Nothing in this box is a value the index holds, and none of it opens a receipt.
What this page does not cover
This is a family of records that read alike. It is not a shared vulnerability, not an inventory, and not a statement that one fix closes the rest. Each record's own state, its own dates and its own receipts are on its own page.
Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.
Everything this vendor has, including records outside this family:
7 records, read from the index as it stood on 20 Sep 2026. Every row opens the record it names, and every value on that record opens its own receipt.