HabrJuly 28, 2026🇷🇺Translated from Russian

SOC Incident Analysis Exposes Active Exploitation of CVE-2025-53770 SharePoint ToolShell Auth Bypass and RCE

SOC analysts have published a detailed incident report on Letsdefend SOC342, covering the exploitation of CVE-2025-53770 — a critical SharePoint ToolShell authentication bypass and remote code execution vulnerability.

The alert was generated by the rule “CVE-2025-53770 SharePoint ToolShell Auth Bypass and RCE” after detecting a suspicious unauthenticated POST request to ToolPane.aspx with an abnormally large Content-Length and a spoofed referer pointing to /layouts/SignOut.aspx. The request was allowed by the security control, indicating the payload reached the server.

Initial Triage and Vulnerability Confirmation

Analysts confirmed the server was likely vulnerable because the observed behavior matched public exploitation indicators published by CISA. The source IP 107.191.58.76 was already listed in the CISA advisory and scored malicious on VirusTotal (10/92 vendors).

Network logs showed the POST request successfully reached the SharePoint server. Subsequent process telemetry revealed w3wp.exe (the IIS worker process) spawning PowerShell with the flags -nop -w hidden -e, followed by Base64-decoded commands that dumped ASP.NET machine keys.

Post-Exploitation Activity

The extracted keys would allow an attacker to forge and sign ViewState payloads, achieving unauthenticated remote code execution. The same w3wp.exe process later launched csc.exe to compile C# source code dropped in C:\Windows\Temp\payload.cs.

Attackers also created a malicious file at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\TEMPLATE\LAYOUTS\spinstall0.aspx that used an ActiveX object (CLSID ADB880A6-D8FF-11CF-9377-00AA003B7A11) to execute or download additional payloads when a user visited the page.

  • Network IOC: 107.191.58.76 (C2 and payload hosting)
  • File hashes (SHA-256): 10e01ce96889c7b4366cfa1e7d99759e4e2b6e5dfe378087d9e836b7278abfb6 (machinekey.aspx), 92bb4ddb98eeaf11fc15bb32e71d0a63256a0ed826a03ba293ce3a8bf057a514 (spinstall0.aspx)
  • Process chain: w3wp.exe → powershell.exe → csc.exe → cmd.exe → powershell.exe

Containment Actions

After confirming compromise, the server was isolated. Recommended remediation steps include blocking the malicious IP, deleting the dropped files, adding the observed hashes to blocklists, patching SharePoint to a safe version, and rotating all ASP.NET cryptographic keys.

Related articles

AntiMalwareVulnerabilities & Exploits

VoLTE Video Call Vulnerability Grants Kernel Access on Unisoc Android Chips

Researchers from SSD Secure Disclosure have disclosed a two-stage attack chain that achieves remote kernel access on Android devices powered by Unisoc chipsets. The exploit begins with a remote code execution flaw in the modem firmware that is triggered by a specially crafted VoLTE video call. Once code executes on the modem, a second privilege-escalation issue abuses shared physical memory between the modem and application processor to reach Android kernel memory. The attack requires an attacker-controlled 4G network and VoLTE infrastructure, and the victim must answer the incoming video call. Vulnerable chip families include T606, T612 and T7250, found in devices such as the Motorola E13, Realme C33 and Xiaomi Redmi A5. No patch or CVE identifier has been issued by Unisoc, and the August Android security bulletin does not address the issue.

安全客Vulnerabilities & Exploits

SAP Commerce Cloud CVE-2026-58231 Critical Flaw Exploited in the Wild Just Three Days After Patch

SAP Commerce Cloud has been hit by a maximum-severity vulnerability tracked as CVE-2026-58231 that carries a CVSS score of 10.0. The flaw resides in the Data Hub Adapter component and allows unauthenticated remote code execution via a single crafted HTTP request. SAP released the official patch on 11 August, yet honeypots recorded the first exploitation attempts only three days later on 14 August. More than 4,200 internet-facing SAP Commerce Cloud instances have been identified worldwide, primarily in Europe and North America. Researchers note that AI-assisted patch analysis enabled attackers to weaponize the fix at unprecedented speed. Organizations are urged to apply the updates to versions 2211.55 or 2211-jdk21.17 immediately and restrict access to the affected endpoints in the meantime.

安全客Vulnerabilities & Exploits

WordPress Login Page Exposed to Critical XSS2Shell Flaw CVE-2026-64638: Over 11,000 Sites Attacked Across 67 Countries

WordPress core login page vulnerability CVE-2026-64638 enables unauthenticated attackers to trigger reflected XSS that can escalate to full server compromise. The flaw stems from mismatched HTML sanitization between two filtering layers on the wp-login.php page, allowing malicious payloads to execute in the site origin. Imperva observed automated campaigns hitting more than 11,000 sites with hundreds of thousands of requests, predominantly affecting U.S. targets in gaming, education, and finance sectors. Successful exploitation chains the XSS into WordPress REST API and application password creation when an administrator is logged in, ultimately allowing malicious plugin uploads. Official patches are available in WordPress 7.0.3 and backported releases down to 4.7; administrators are urged to verify versions, audit user accounts, and inspect plugin directories immediately.

HabrVulnerabilities & Exploits

WireGuard Kernel Module Silently Overwrites AllowedIPs in Trie, Breaking Peer Routing Without Errors

The WireGuard kernel module stores AllowedIPs in a single prefix trie per device rather than per peer, causing exact-match insertions of identical CIDR prefixes to reassign nodes and remove them from the previous peer's list. This behavior silently drops routing for affected peers while handshakes and inbound traffic continue, leading to one-way connectivity failures and frame errors. The issue affects road-warrior setups using 0.0.0.0/0, mesh networks, Kubernetes CNI plugins such as Cilium and Calico, and network operating systems including VyOS and OPNsense. No warning is emitted by wg, wg-quick, or the kernel on overwrite, and the longest-prefix-match lookup ensures only equal-length prefixes collide. The root cause resides in allowedips.c where rcu_assign_pointer redirects the trie node and list_move_tail detaches it from the original peer. The same logic appears across Linux, wireguard-go, wireguard-nt, FreeBSD, and OpenBSD implementations.