wp2shell WordPress RCE: Patch Now

wp2shell WordPress RCE

wp2shell WordPress RCE is now a two-CVE chain in CISA’s Known Exploited Vulnerabilities catalog — and it lets a completely unauthenticated attacker execute code on a default WordPress install with no plugins involved. If you run self-hosted WordPress and haven’t confirmed the July 17 auto-update landed, check today. What Happened wp2shell WordPress RCE combines two…

Read More

CVE-2026-50522 SharePoint RCE: Patching Isn’t Enough

CVE-2026-50522 SharePoint RCE

CVE-2026-50522 SharePoint RCE is now the third actively exploited remote code execution flaw hitting Microsoft’s on-premises collaboration platform in three weeks — and this one lets attackers steal cryptographic machine keys that remain valid long after the server is patched. If you run SharePoint Server 2016, 2019, or Subscription Edition on-premises, patching is no longer…

Read More

EY Third-Party Data Breach: 15 Days Inside Helpdesk

EY third-party data breach

EY third-party data breach: attackers spent 15 days inside a support-ticketing platform used by Ernst & Young’s tax practice, walking out with client tax filings, Social Security numbers and financial account data before anyone noticed — the firm’s third vendor-side security failure in under three years. What Happened This EY third-party data breach ran from…

Read More

ServiceNow CVE-2026-6875 RCE: Sandbox Escape Exploited

ServiceNow CVE-2026-6875 RCE

ServiceNow CVE-2026-6875 RCE is now being actively exploited: a critical, unauthenticated sandbox-escape vulnerability in the ServiceNow AI Platform is under attack barely a week after the vendor shipped a fix, and ServiceNow’s own advisory has not yet caught up with independent confirmation of the exploitation. What Happened ServiceNow CVE-2026-6875 RCE traces back to a sandbox-escape…

Read More

AsyncAPI npm Supply Chain Attack: No Token Stolen

AsyncAPI npm supply chain attack

The AsyncAPI npm supply chain attack shows that neither of the two controls teams were told to trust — cryptographic provenance and blocking install scripts — actually stopped it: an attacker published four trojanized packages with valid SLSA/OIDC provenance attestations, without ever stealing an npm token, and the payload runs regardless of –ignore-scripts. What Happened…

Read More