Organizations worldwide are scrambling to patch critical SharePoint vulnerabilities that attackers are actively exploiting with devastating precision. Microsoft's emergency security bulletin reveals that CVE-2025-53770 and CVE-2025-53771 carry a staggering 9.8 severity rating, allowing unauthenticated attackers to execute arbitrary code and deploy web shells on vulnerable SharePoint servers. The ""ToolShell"" exploit chain, first demonstrated in May 2025, has evolved into a sophisticated attack vector targeting on-premises SharePoint installations globally. According to Ars Technica's security analysis, these vulnerabilities enable attackers to access restricted functionality, install persistent backdoors, and exfiltrate sensitive corporate data without authentication. What makes this particularly alarming is the web shell deployment pattern. Attackers are installing files named ""spinstall0.aspx"" and variations, extracting MachineKey data to maintain unauthorized access long after initial compromise. Microsoft's security team has documented active exploitation across multiple industries, prompting their rare out-of-band emergency patch release on July 19, 2025. The silver lining? SharePoint Online users in Microsoft 365 remain unaffected. However, organizations running on-premises SharePoint servers face immediate risk. Microsoft's guidance emphasizes applying security updates immediately, enabling Microsoft Defender for Endpoint, and rotating ASP.NET machine keys as critical first steps. This incident underscores a harsh reality about enterprise security: even the most trusted platforms can become attack vectors overnight. The speed of exploitation following public disclosure reminds us that patch management isn't just IT housekeeping—it's business survival in our interconnected digital landscape. #CyberSecurity #SharePoint #Microsoft #VulnerabilityManagement #InfoSec #EnterpriseRisk #PatchManagement #ZeroDay #ThreatIntelligence #BusinessContinuity
More Relevant Posts
-
🚨 Critical Security Alert: CVE-2025-53770 – SharePoint Under Active Attack Microsoft has confirmed a critical Remote Code Execution (RCE) vulnerability impacting on-premises SharePoint Server — tracked as CVE-2025-53770 — and exploitation is already happening in the wild. 🔴 Severity: Critical (CVSS 9.8) 🕵️♂️ Impact: Allows unauthenticated attackers to execute code remotely ☁️ Not Affected: SharePoint Online (Microsoft 365) ⸻ 🔥 Why this matters SharePoint often sits at the heart of enterprise collaboration. Once compromised, attackers can gain a foothold to move across the network, steal data, deploy ransomware, and maintain persistence. ⸻ ✅ What organizations must do now 🔹 Patch immediately – Apply the latest security updates on all on-prem SharePoint servers 🔹 Harden & monitor – Enable AMSI integration and verify endpoint protection is active 🔹 Assume breach & validate – Hunt for web shells and suspicious SharePoint activity 🔹 Rotate machine keys – Prevent attacker persistence even after patching ⸻ 🧠 Final Thoughts If your organization runs SharePoint Server on-prem, treat this as a top-priority incident. Speed of response is critical — patching alone is not enough without validation. If you’d like, I can share a ready-to-use internal communication template for IT and security leaders, along with a technical checklist for SOC teams. Stay safe, stay updated. 🔐 #cybersecurity #sharepoint #vulnerability #CVE2025 #infosec #patchnow #securityalert
To view or add a comment, sign in
-
🚨 ToolShell Exploits in Microsoft SharePoint: A Wake-Up Call for IT and Security Leaders In the months following Microsoft’s July 2025 patch, multiple China-linked threat groups—including Linen Typhoon, Violet Typhoon, and Salt Typhoon—have exploited CVE-2025-53770, a critical SharePoint vulnerability now known as “ToolShell” thehackernews.com. 🔍 What we know: CVE-2025-53770 enables authentication bypass and remote code execution on on-prem SharePoint servers. Despite being patched, the flaw was rapidly weaponized in espionage campaigns targeting: A telecom provider in the Middle East Government agencies in Africa and South America A U.S. university and a European finance firm thehackernews.com Attackers deployed tools like ShadowPad, Zingdoor, and KrustyLoader—indicating long-term persistence and credential theft objectives thehackernews.com. Some campaigns also leveraged PetitPotam (CVE-2021-36942) for privilege escalation and domain compromise thehackernews.com. 🧠 Why this matters: ToolShell is a case study in patch lag, threat actor agility, and the limits of perimeter defense. The flaw bypasses previous patches (CVE-2025-49704/49706), raising concerns about patch efficacy and regression testing. The breadth of targets—telecom, education, finance, and government—underscores the cross-sector risk of unpatched collaboration platforms. 💬 For CISOs, MSPs, and infrastructure leaders: Reassess your SharePoint exposure—especially on-prem deployments. Validate patch coverage and monitor for post-exploitation behaviors (DLL side-loading, credential theft, lateral movement). Strengthen vendor patch validation processes and threat intel integration. This isn’t just a SharePoint issue—it’s a governance issue. How are we ensuring that patching, detection, and response are aligned across silos? #CyberSecurity #SharePoint #ToolShell #CVE202553770 #PatchManagement #ThreatIntelligence #MSP #CISO #ZeroDay #InfrastructureResilience #VendorAccountability #SecurityOps #Governance Article Link - https://lnkd.in/gcDUA9St
To view or add a comment, sign in
-
Another Day, Another Data Exposure — This Time It's the U.S. Air Force The Air Force is investigating a privacy incident after personally identifiable information (PII) was unintentionally exposed through a Microsoft SharePoint site. The full scope hasn’t been disclosed yet, but here’s what we do know: this wasn’t a breach by some outside hacker group. It was a configuration issue — the kind that happens quietly, inside the system, when access settings aren’t handled carefully. Sound familiar? This kind of slip-up happens all the time in the business world. Files get shared to "Everyone," folders are synced to the wrong cloud location, permissions are never reviewed, and suddenly sensitive data is out there for the wrong people to see — or worse, download and share. Here’s the uncomfortable truth: these aren’t sophisticated cyberattacks. They’re preventable mistakes. And they don’t require elite hacking skills to exploit — just someone who stumbles across something they weren’t supposed to. When even the military is making these kinds of mistakes, it’s a wake-up call for every organization. Because if data exposure can happen at that level, it can absolutely happen at yours. Ask yourself: do you know who has access to what in your organization’s systems? Are permissions reviewed regularly, or set once and forgotten? Do you know how many files are shared publicly — or worse, have been for years? It’s not about scaring people. It’s about being honest. Most organizations don’t have a technical problem — they have a visibility problem. They can’t fix what they can’t see. And if they’re not looking, they’ll never know something’s exposed until it’s too late. Data loss isn’t always a headline-grabbing breach. Sometimes it’s just a quiet leak in your own SharePoint settings. #DataPrivacy #InformationSecurity #CyberRisk #SharePoint #AccessControl #CloudSecurity #Infosec #SecurityAwareness #DataGovernance #DigitalHygiene https://lnkd.in/em3HV5vr
To view or add a comment, sign in
-
Your SharePoint server isn’t aging. It’s expiring. And when support ends, so does your security. Four new zero-days (CVE-2025-49704, 49706, 53770, 53771) are already being exploited by Chinese nation-state actors. On July 14, 2026, Microsoft ends support for SharePoint 2016 and 2019. From that point on? Every new vulnerability stays open. Forever. Legacy collaboration tools can’t keep up. ❌ Fragmented systems ❌ Manual audits ❌ Perimeter-based security No wonder FedRAMP, CMMC, GDPR, and HIPAA programs fail audits year after year. ✅ Kiteworks replaces those silos with one FedRAMP Ready, CMMC-aligned Private Data Network. 👉 It’s built for zero trust. 👉 Built for continuous compliance. 👉 Built for complete visibility across email, file, and API exchanges. Don’t wait for the next exploit. If it’s private, Kite it. #SharePoint #ZeroTrust #Cybersecurity #Compliance
To view or add a comment, sign in
-
Microsoft SharePoint Zero-Day: When Trust Becomes a Vulnerability We often talk about Zero Trust — but what happens when the software you “trust” the most becomes your biggest weakness? In July 2025, researchers revealed a critical zero-day vulnerability in Microsoft SharePoint that was already being exploited in the wild. Targets included U.S. government agencies, energy companies, and universities, with attackers leveraging the flaw to gain persistence and quietly exfiltrate sensitive data. 🔍 What made this different It wasn’t a ransomware event or a brute-force attack. It was a stealthy, supply-chain style compromise exploiting a trusted enterprise platform. Victims had properly configured networks and standard patch processes — yet they were still exposed. Even after Microsoft’s emergency patch, compromised credentials and tokens remained a long-tail risk. 🧠 Key takeaways Patch management ≠ complete protection. You also need behavior-based detection and forensic visibility. Vendor trust ≠ vendor immunity. Even the most reputable vendors can have exploitable flaws. Supply-chain exposure is now a top-tier national security concern. Every dependency — from APIs to SaaS integrations — extends your attack surface. Response coordination is essential. Many organizations discovered they didn’t have clear processes for engaging with vendors during an active exploitation event. 🧰 What teams should do Conduct a software bill of materials (SBOM) review to understand dependencies. Implement threat-hunting specifically focused on vendor tool anomalies. Include third-party compromise scenarios in tabletop exercises. Strengthen your detection engineering to identify lateral movement originating from “trusted” software. 💡 Final insight: Cybersecurity isn’t just about defending your perimeter — it’s about defending your trust relationships. In 2025, visibility is the new trust. #CyberSecurity #Microsoft #ZeroDay #ThreatIntel #SupplyChainSecurity #CISO #Resilience
To view or add a comment, sign in
-
Hybrid Cloud Security Overhaul: IAM, Conditional Access & IRP in Action As part of my cybersecurity portfolio, I led a simulated remediation project for SecureCart Inc., a fictional hybrid-cloud e-commerce enterprise using Microsoft Entra ID and Microsoft 365 Business Premium. Audit Findings: • Excessive IAM privileges for non-admins • Misaligned group memberships • Unrestricted guest access to SharePoint/Teams • No formal incident response plan (IRP) What I Did: ✅ Reconfigured IAM roles and group memberships using Entra ID ✅ Scoped guest access to marketing-only resources ✅ Enforced MFA and location-based Conditional Access policies ✅ Simulated phishing attack and executed full NIST 800-61 IRP ✅ Captured all remediations via annotated screenshots for audit and portfolio use Tools Used: Microsoft Entra Admin Center | Microsoft 365 Defender | Authenticator | Word & PowerPoint | Snipping Tool Skills Demonstrated: RBAC design | Conditional Access | Threat detection | Log analysis | IRP execution | Professional documentation Key Takeaways: • Least privilege is non-negotiable • Conditional Access = identity firewall • Defender + Entra logs = forensic gold • A tested IRP is essential for cloud resilience This project reflects my ability to translate audit findings into actionable controls, align with compliance frameworks, and deliver structured, portfolio-ready documentation. If you're working on hybrid-cloud security or IAM governance, let’s connect and share insights. #Cybersecurity #CloudSecurity #IAM #Microsoft365 #EntraID #IncidentResponse #DefenderForOffice365 #RBAC #SecurityEngineer #NIST80061 #ProfessionalDocumentation
To view or add a comment, sign in
-
🚨 ToolShell Exploits in Microsoft SharePoint: A Global Threat Landscape Unfolds 🌍 Chinese threat actors have weaponized the ToolShell vulnerability (CVE-2025-53770) in on-prem SharePoint servers, targeting critical infrastructure across four continents, including government agencies, universities, telecom providers, and finance firms. 🔍 Key Technical Insights: ToolShell is a zero-day RCE flaw that bypasses CVE-2025-49706 and CVE-2025-49704. Attackers used webshells for persistent access, followed by DLL side-loading of: 🛠️ Zingdoor (Go-based backdoor) 🐛 ShadowPad Trojan 🦀 KrustyLoader (Rust-based loader) 🧬 Sliver (post-exploitation framework) Legitimate executables from Trend Micro and BitDefender were abused for stealth. Credential dumping via ProcDump, Minidump, and LsassDumper. PetitPotam (CVE-2021-36942) used for domain compromise. Living-off-the-land tools included Certutil, GoGo Scanner, and Revsocks. 📊 Symantec’s report reveals a broader set of Chinese APTs involved than previously known, including Salt Typhoon, Budworm, Sheathminer, and Storm-2603. 🔐 This campaign underscores the urgency of patching vulnerable SharePoint instances and monitoring for lateral movement and post-exploitation frameworks. #CyberSecurity #Infosec #ThreatIntel #APT #SharePoint #ToolShell #ZeroDay #RCE #Microsoft #DLLSideLoading #RustMalware #CredentialDumping #LivingOffTheLand #Symantec #BlueReport2025 #CVE2025 #SecurityOps #IncidentResponse #SOC #ThreatHunting
To view or add a comment, sign in
-
A zero-day vulnerability in Microsoft SharePoint has been actively exploited in the past 24 hours, allowing remote code execution (RCE) via code injection. A malicious payload identified as a Trojan HTML/Sharept.RCE!tr has also been observed. The attacks originated from multiple global locations including Ashburn, Toronto, Frankfurt, and Istanbul, with primary targets in the United States, UAE, Luxembourg, France, Germany, and the Netherlands. The most targeted industries include: 🔹 Government 🔹 Banking and Financial Services 🔹 Cloud and Infrastructure Providers 🔹 Energy and Utilities 🔹 Healthcare 🔹 Education 🔹 Telecommunications and IT Recommended urgent actions: Immediately patch all Microsoft SharePoint systems. Enable and synchronize IPS signatures, particularly from FortiGuard. Isolate and investigate any suspicious SharePoint servers. Scan for the presence of the HTML/Sharept.RCE!tr Trojan. Monitor and restrict PowerShell privileges across systems. Incident response plans should be activated, and cybersecurity teams should assess exposure. If you need help drafting an internal advisory or a tailored IR plan, feel free to reach out. #CyberSecurity #SharePoint #ZeroDay #ThreatIntel #IncidentResponse #FortiGuard #MicrosoftSharePoint Peter A. Steven Masada Satya Nadella Bill Gates Microsoft Security CISA Alumni Group Federal Bureau of Investigation (FBI) FortiGuard Labs
To view or add a comment, sign in
-
CVE ID: CVE-2024-30082 Title: Microsoft SharePoint Server Remote Code Execution Vulnerability Description: A remote code execution vulnerability exists in Microsoft SharePoint Server. An authenticated attacker with Site Owner privileges could upload a specially crafted file to the server, which could then lead to arbitrary code execution in the context of the SharePoint application pool. This vulnerability does not require user interaction beyond the initial file upload. No public exploit code or active exploitation is currently known. [Microsoft Advisory] Severity Level: CVSS v3.1: 8.8 High Affected Products: Microsoft SharePoint Server Subscription Edition, Microsoft SharePoint Server 2019, Microsoft SharePoint Server 2016 Potential Impact: Successful exploitation could allow an attacker to gain full control over the affected SharePoint server, leading to data compromise, service disruption, or further network penetration. Recommended Mitigation Strategies: Immediately apply the security updates released by Microsoft. For SharePoint Server Subscription Edition, apply the June 2024 Public Update. For SharePoint Server 2019, apply KB5002626. For SharePoint Server 2016, apply KB5002625. Regularly review and restrict Site Owner permissions to only trusted individuals. Implement network segmentation and monitor SharePoint server logs for unusual activity. Stay vigilant and prioritize these updates. Proactive defense is our strongest tool against such high-impact vulnerabilities. Share this to keep our community informed and secure! Hashtags: #CVE #SharePoint #Microsoft #Vulnerability #RCE #Cybersecurity #PatchTuesday #InfoSec
To view or add a comment, sign in
-
JUST IN: Hackers linked to Ch*na exploited a “patched” Microsoft SharePoint flaw to break into networks across four continents. It wasn’t just spying. They found a way to bypass the patch that fixed a previous bypass. What makes this campaign particularly insidious is the depth of the post-exploit chain: after the unauthenticated breach, attackers deploy web shells, target MachineKey values, and forge authentication tokens. Once inside, the infrastructure runs as trusted. The result is that "the breach doesn’t just grant access; it becomes a hidden residency." For companies running broad-scale enterprise stacks, this exposure means even a *one-line exploit* can cascade into full-domain compromise. For non-IT teams, the message is simple. If your server is internet-facing and unpatched, you aren’t just living with risk. You’re hosting it. So, here are our recommendations: 1. Keep internet-facing servers fully patched within 24–48 hours of a security update and never expose admin panels or collaboration tools like SharePoint directly to the web. 2. Segment those systems behind VPN or zero-trust gateways, enforce multi-factor authentication, and monitor for web-shell or anomalous traffic activity. Basically, treat every public-facing server as a potential breach entry, not a convenience. https://lnkd.in/g4r6fev3 #auguryit #cysec
To view or add a comment, sign in