Hosts, IPs, or URLs, one per line. Empty input uses localhost.
Detect
Fingerprints SharePoint and flags CVE-2025-53770 by version. No probe.
Confirm
Unauthenticated GET of ToolPane with a SignOut referer. No ViewState gadget. Advisory
Collect
Merges per-host detect and confirm rows.
Report
Counts checked, product, affected, and confirmed.
Overview
This workflow finds Microsoft SharePoint Server and sorts each host by whether its version falls in the CVE-2025-53770 range. CVE-2025-53770 is unauthenticated ToolPane access that leads to ViewState deserialization. Confirm only checks that the edit pane answers. It does not deserialize. CISA listed it on KEV after confirmed use. Give it hostnames, IP addresses, or URLs you are authorised to test. The workflow fingerprints the product from a public page, reads the version from the MicrosoftSharePointTeamServices header when present, and compares that number to the range table in the graph. Every host comes back affected or not, so a fleet advisory becomes an evidenced list for exposure management. Version flag is first. Hosts in range get a second node that GETs ToolPane with a SignOut referer. It does not send a ViewState gadget.
Run it on a schedule when the estate changes. New hosts and delayed patch windows are the reason the same check is worth more the second week than the first.
Pipeline
Read the target list. Hosts, URLs, or ranges, one per line, become the scope.
Fingerprint each host as SharePoint, then read the version and compare it to the CVE-2025-53770 floors in the graph.
Confirm only those flagged hosts with an unauthenticated GET of /_layouts/15/ToolPane.aspx and a SignOut referer. It does not send a ViewState gadget.
Collect the per-host rows: product match, version, affected flag, confirmed flag, and any fetch error.
Emit the summary counts: hosts checked, product hits, affected, confirmed, and errors.
Inputs
Target list. Hostnames, IP addresses, CIDR ranges, or URLs, one per line. JSONL with a url field also works. Point it at scope you are authorised to test.
Outputs
results.jsonl. One row per host: URL, whether SharePoint was detected, the version read, the affected flag, and whether the ToolPane surface answered.
summary.json. Counts across the list: targets, product hits, affected, confirmed, and errors.
Integrations
HTTP. Unauthenticated GET to the product surface and, on flagged hosts only, ToolPane with a SignOut referer. No ViewState gadget.
Sample output
The records below are illustrative and do not come from a real run. They show one SharePoint host inside the CVE-2025-53770 range, one patched host, and one host that is not the product.
On-prem SharePoint Server builds before the July 2025 ToolShell patches. The MicrosoftSharePointTeamServices header is the version source when present. The compare uses the version the product itself served.
Does a confirmed row mean ToolShell RCE?
No. Confirm only GETs ToolPane with a SignOut referer. It does not send a ViewState gadget. A confirmed row means the edit pane still answers.
Is this check safe on production?
Yes. Fingerprint is read-only GET. Confirm is an unauthenticated ToolPane GET, only on hosts already in range. It does not log in or deserialize.
Does the check need credentials?
No. It fingerprints the public page the way an external scanner would.
What is CVE-2025-53770?
Unauthenticated ToolPane access that leads to ViewState deserialization. CISA listed it on KEV after confirmed use. This workflow flags by version, then confirms that ToolPane still answers.