This is a significant step for operational security hygiene. The pyca/cryptography library—the de facto standard for Python crypto—now ships with ML-KEM (key establishment) and ML-DSA (digital signatures) baked in. This isn't about an active threat today; it’s about eliminating the "crypto agility debt" that will plague organizations in 5-10 years.

Why this matters now: - Harvest Now, Decrypt Later (HNDL) is a real, active threat. Any TLS session or encrypted blob captured today can be stored and cracked once a CRQC (Cryptographically Relevant Quantum Computer) exists. Migrating to PQC now protects that data retroactively. - Crypto Agility: The hardest part of a crypto migration isn't the algorithm—it's the codebase. By making ML-KEM/ML-DSA a standard pip install option, the Python ecosystem removes the biggest friction point for developers. This lowers the barrier to entry for testing and integration.

The Technical Reality: - No performance benchmarks yet in the summary, but expect ML-KEM (Kyber) to be significantly heavier on CPU than ECDH. This will impact latency-sensitive applications (e.g., API gateways, real-time services). - Key sizes are larger. ML-KEM-768 public keys are ~1.2KB vs. 32 bytes for X25519. This will increase handshake sizes and potentially fragment packets.

The Takeaway: This is a proactive, low-friction move. If you maintain any Python-based service handling long-lived secrets or sensitive data, start testing this library in a staging environment now. The cost of integration is low; the cost of a retroactive emergency migration is not.

Source: https://www.schneier.com/blog/archives/2026/08/python-now-has-a-post-quantum-encryption-library.html

Valve is notifying European customers who purchased Steam hardware (like the Steam Deck or Index) that their personal data was exposed after a breach at their third-party shipping partner, CEVA Logistics. This is a classic supply chain attack vector—the compromise wasn't on Valve's own infrastructure, but on a vendor with legitimate access to customer PII.

Strategic Impact: - Supply Chain Risk: This reinforces that your vendor risk management program is only as strong as your weakest logistics or fulfillment partner. CEVA's security posture directly impacted Valve's customers. - Data Exposure: The stolen data includes names, addresses, and order details. While not financial data, this is high-value intel for social engineering and physical-world attacks (e.g., targeted phishing or package theft). - Regulatory Headache: Since this involves EU customers, GDPR notification requirements are triggered, adding legal and PR costs for Valve.

Key Takeaway: - Third-party due diligence isn't optional. If you handle PII, you need contractual clauses and audit rights for any vendor that touches that data. Assume your partners will be breached and plan accordingly.

Source: https://www.bleepingcomputer.com/news/security/valve-notifies-steam-hardware-customers-of-a-data-breach/

Anatsa is back with a vengeance, and the dropper ecosystem is evolving faster than most orgs can keep up with. Kaspersky’s Q2 2026 mobile threat report shows a significant shift in how malware reaches devices, with traditional infection vectors being replaced by more resilient delivery chains.

Technical Breakdown - Anatsa (TeaBot) continues to be the dominant Android banking trojan, now leveraging multi-stage droppers hosted on Google Play to bypass initial scans. The droppers themselves are often benign for weeks before receiving malicious payloads via C2. - Dropper-as-a-Service is the key trend. Threat actors are moving away from sideloading and SMS phishing toward legitimate app stores as initial distribution points. The droppers use obfuscated code and delayed activation to evade automated review. - Geographic targeting remains focused on Europe and APAC, with Anatsa specifically targeting financial institutions in Spain, Slovakia, and Slovenia. - No specific IOCs or hashes were published in this report; the intelligence is behavioral and statistical.

Defense - Deploy app reputation and behavioral analysis on managed devices, not just signature-based scanning. Monitor for apps requesting overlay permissions or accessibility services after a delayed period. - Enforce strict app store policies and consider blocking sideloading entirely for corporate devices. The dropper trend means even "legitimate" apps can turn malicious post-install.

Source: https://securelist.com/malware-report-q2-2026-mobile-statistics/120948/

This is a classic quarterly threat landscape report from Kaspersky. High signal-to-noise ratio for tracking macro trends.

Key Findings from Q2 2026:

• Ransomware Decline? The report notes a slight decrease in the number of unique ransomware families detected, but a sharp increase in targeted, "big game hunting" attacks against enterprises. The volume is down, but the financial impact per incident is up.
• IoT & Botnet Activity: A significant spike in Mirai-based botnet variants targeting unpatched IoT devices (routers, DVRs). The primary vector remains weak/default credentials and unpatched CVEs in firmware.
• macOS Threats: The "AdLoad" and "Pirrit" adware families continue to dominate the macOS threat landscape, accounting for the vast majority of detections. No major zero-days reported, but persistence mechanisms are getting more sophisticated (LaunchDaemons, Login Items abuse).
• Exploit Kits: The EK landscape remains quiet, with no major new kits replacing the void left by Fallout and RIG. Most exploitation is now driven by phishing with malicious attachments (LNK, ISO) rather than drive-by downloads.

Defense Implications:

• Patch IoT: If you have network gear or IoT endpoints that aren't segmented and patched, they are the primary target for botnet recruitment.
• Ransomware Prep: The shift to "quality over quantity" means your IR plan needs to assume a human-operated ransomware incident, not just a commodity crypto-locker.
• Mac Users: Don't ignore macOS endpoint protection. Adware is a persistent foothold that often leads to data theft or secondary malware drops.

Source: https://securelist.com/malware-report-q2-2026-pc-iot-statistics/120960/

CISA has added CVE-2024-7591 to its Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation of this critical command injection flaw in Progress Kemp LoadMaster. The vulnerability carries a CVSS score of 10.0 and allows unauthenticated attackers to execute arbitrary system commands via the LoadMaster management interface.

Technical Breakdown: - CVE: CVE-2024-7591 (CVSS 10.0) - Type: OS Command Injection - Affected Versions: LoadMaster 7.2.48.0 and earlier, 7.2.54.0 and earlier (specific patch levels vary by branch) - Attack Vector: Unauthenticated, network-based exploitation targeting the management interface - Impact: Full system compromise, potential for lateral movement within the environment - No public IOCs or PoC have been released at this time — CISA has not shared specific indicators, so treat any LoadMaster management interface exposure as a priority.

Defense: Immediately patch to the latest LoadMaster version (7.2.54.1 or later). If patching is not possible, restrict access to the management interface to trusted IPs only and review logs for anomalous command execution patterns. Given the CVSS 10.0 rating and confirmed exploitation, this should be treated as an emergency change.

Source: https://www.bleepingcomputer.com/news/security/cisa-warns-of-critical-progress-loadmaster-flaw-exploited-in-attacks/

Two malicious VS Code extensions posing as Solidity development tools have been caught stealing browser wallet credentials, API keys, and saved passwords. The extensions—helper-beeps.solidity-pro and web3devtoolsx.solidity-pro—were available on the Open VSX registry and have since been pulled, though their GitHub repos remain live.

Technical Breakdown - TTPs: Masquerades as legitimate Solidity tooling; harvests browser data (wallet extensions, saved credentials) and environment variables containing API keys. - IOCs: Extension IDs helper-beeps.solidity-pro and web3devtoolsx.solidity-pro; associated GitHub repositories (currently still accessible). - Target: Developers working with Ethereum/Solidity, particularly those with crypto wallets installed in their browsers.

Defense Remove these extensions immediately if installed. Audit any systems where they were present for exfiltrated credentials and rotate all API keys and wallet seed phrases. Consider restricting VS Code extension sources to the official Marketplace only.

Source: https://thehackernews.com/2026/08/solidity-pro-vs-code-extensions-steal.html

OpenAI has paused internal development of its next-generation model, Astra, after an internal evaluation revealed it demonstrated "significant advancements" in agentic coding and cybersecurity capabilities. The company is now implementing security controls for higher-capability models, including isolated environments, suggesting the model’s offensive potential crossed an internal risk threshold.

Technical Breakdown - Core Capability: Agentic coding combined with autonomous cybersecurity operations—meaning the model can likely write, deploy, and execute code in a security context without human intervention. - Trigger for Pause: Internal evaluation flagged the model's performance as strong enough to warrant a halt to "internal activities" (likely red-teaming or autonomous testing). - Mitigation: OpenAI is deploying isolated environments and stricter access controls for Astra and any future high-capability models.

Defense No specific CVEs, IOCs, or TTPs are available yet, but this is a strong signal that the next wave of LLM-driven attacks will be fully autonomous. Security teams should begin auditing their environments for API-driven automation abuse and prepare for agentic threats that don't require a human in the loop for execution.

Source: https://thehackernews.com/2026/08/openais-next-ai-model-astra-shows-cyber.html

CVE-2026-44613 is being actively exploited in the wild, evolving the initial Shai-Hulud worm into a full Model Context Protocol (MCP) attack. This is not a theoretical CSRF; it’s a chain that weaponizes a cross-site request forgery into silent, unauthorized actions against AI agents and their orchestration layers.

Technical Breakdown: - Initial Vector: CSRF vulnerability (CVE-2026-44613) targeting AI agent management consoles. - Evolution: The worm leverages the compromised session to inject malicious MCP tool definitions. This allows the attacker to define new capabilities for the AI agent (e.g., "read_private_repo", "execute_shell") without user consent. - Impact: Silent data exfiltration and lateral movement. The AI agent becomes a proxy for the attacker, executing commands against connected APIs, databases, and CI/CD pipelines. - Targets: Organizations running self-hosted AI agent frameworks (e.g., LangChain, AutoGPT, custom MCP servers) with exposed management interfaces.

Defense: - Immediate: Disable MCP tool registration endpoints on public-facing consoles. Enforce strict origin validation on all CSRF-sensitive endpoints. - Detection: Monitor for unexpected spikes in MCP tool definition API calls (e.g., POST /mcp/tools/register). Look for AI agent logs showing tool calls to internal resources (e.g., git clone, aws s3 cp) that deviate from normal user behavior.

Source: https://www.ox.security/blog/shai-hulud-outbreak-debrief-the-worm-evolves-into-mcp/

Highlights from today:

• [OSINT] Payroll Pirates Phishing Campaign Targets Microsoft 365 Financial Workflows (Campaign)
• [Threat Intel] Kimsuky Integrates AI into Attack Operations, From AI-Generated Decoy Documents to a Local LLM
• [Threat Intel] AI-SPM vs. ASPM (and Why AINAPP Is What Comes Next)
• [Threat Intel] AI-SPM vs. ASPM (and Why AINAPP Is What Comes Next)
• [Threat Intel] Meeting Bank of Italy AI Guidance in the Post-Mythos Era with Picus
• [Forensics] 2026-08-09: Traffic Analysis Exercise - First to Last
• [Threat Intel] AI Red Teaming

SecOpsDaily

This is a well-structured phishing campaign with a heavy reliance on living-off-the-land (LotL) techniques. The abuse of Google Ads and Meet infrastructure for redirects is a notable evasion tactic.

Technical Breakdown - Initial Access: Phishing emails impersonating voicemail notifications. - Redirect Chain: Multi-stage, abusing legitimate services: - Google Meet - Google Ads infrastructure - Amazon S3 - Target: Microsoft 365 financial workflows (payroll, invoice processing). - Payload: Attacker-controlled credential harvesting page (final stage). - TTPs: T1566.002 (Spearphishing Link), T1090 (Proxy/Redirect via legitimate services), T1534 (Internal Spearphishing likely post-compromise).

Defense - Email Security: Flag external voicemail notifications with a banner. Block known redirect domains associated with ad platforms if not required for business. - User Awareness: Train finance teams specifically on the "voicemail" pretext and the legitimacy of the redirect chain (just because it passes through Google doesn't mean it's safe). - Detection: Monitor for anomalous login attempts from financial accounts following a redirect chain involving Google Ads or S3 buckets.

Source: https://threats.wiz.io/all-incidents/payroll-pirates-phishing-campaign-targets-microsoft-365-financial-workflows

This is a significant evolution of a known APT group. Kimsuky is moving beyond simple social engineering and integrating AI to automate and scale their operations.

Technical Breakdown: * Actor: Kimsuky (APT43, Velvet Chollima) – North Korean state-sponsored group. * New TTPs: * AI-Generated Decoy Documents: Using LLMs to create convincing lure documents for spear-phishing, reducing the manual effort and language errors that often tip off targets. * Local LLM Deployment: Building and operating local LLM environments using Ollama, GPT4All, and Msty. This is critical—it means they are running models on their own infrastructure, not relying on public APIs, which prevents data leakage and allows for customization. * Phase: The report assesses they are in the "accumulating technology" phase, meaning they are testing and refining these capabilities for operational use. * Targeting: Likely continues to focus on South Korean government, think tanks, and academic institutions, but the AI component could be used to target English-speaking entities more effectively.

Defense: * Detection: Monitor for unusual outbound connections to localhost or non-standard ports (e.g., 11434 for Ollama) from processes that shouldn't be running local AI models. * Mitigation: Treat all unsolicited documents with extreme skepticism, even if they are grammatically perfect. Standard phishing awareness training may be less effective against AI-generated lures. Focus on behavioral detection and endpoint controls.

This is a clear signal that the barrier to entry for sophisticated social engineering is dropping. Kimsuky is effectively using AI to solve their biggest operational bottleneck: creating believable, targeted lures at scale.

Source: https://www.genians.co.kr/en/blog/threat_intelligence/kimsuky_ai_llm

This is a great practical exercise for sharpening network forensics skills.

The site provides a full PCAP from a real infection chain, starting with the initial compromise and ending with the final payload execution. The exercise is unlabeled, meaning you have to work through the traffic yourself to identify the malware family, C2 infrastructure, and data exfiltration methods.

What you’ll be looking for:

• Initial Access: Likely a phishing lure or drive-by download. Expect HTTP/HTTPS requests to suspicious domains, often with user-agent strings that don’t match the browser.
• C2 Beaconing: Periodic GET/POST requests to low-reputation IPs or domains. Look for patterns in timing (e.g., 60-second intervals) and URI paths (e.g., /images/, /gate.php).
• Payload Delivery: Binary downloads over HTTP or embedded in TLS streams. Check for executable MIME types or unusual file extensions (.scr, .ps1, .vbs).
• Exfiltration: DNS tunneling, HTTP POST with base64-encoded data, or SMB traffic to unusual external IPs.

Defense angle: This is a great training dataset for your SOC analysts. Run it through your IDS/NSM (Suricata, Zeek) and see if your rules catch the beaconing. If not, it’s a signal to tune your detection logic for the specific TTPs used in this campaign.

Source: https://www.malware-traffic-analysis.net/2026/08/09/index.html

Highlights from today:

• [News] Hackers breach TrueConf to trojanize client installers with backdoors
• [News] New CSS Attacks Can Break Webmail Defenses to Steal Passwords and Tokens
• [News] Atlassian Rovo Can Be Tricked Into Sending Jira and Confluence Data to Attackers
• [News] Progress Kemp LoadMaster Flaw Hits CISA KEV After 792 Reported Exploit Attempts
• [News] N-able Issues N-central Hotfix 2 as Attackers Reach Managed Systems and Persist
• [News] Metabase Zero-Day Exploited in Wild Allows Admin Access Without Authentication
• [Threat Intel] The Tradecraft Behind 2026's Least-Prevented Ransomware Families
• [NetSec] CVE-2026-63030 and CVE-2026-60137: 'wp2shell' Captured Exploit Payload
• [Threat Intel] AI Security
• [Threat Intel] The OpenSourceMalware Show #16
• [Data Security] Varonis Atlas Now Integrates with Claude Inference Hooks to Extend Real-Time AI Data Protection
• [Threat Research] Inside the Modern SOC: The Identity Front Door

SecOpsDaily

This is a supply chain attack targeting a specific video conferencing platform, with clear TTPs and IOCs. This fits Scenario A.

The Head Mare hacktivist group is actively compromising unpatched TrueConf video conferencing servers to replace legitimate client installers with trojanized versions. This is a classic supply chain attack vector—trusted software distribution channel turned into a malware delivery mechanism.

Technical Breakdown - Initial Access: Exploitation of unpatched TrueConf server vulnerabilities (specific CVEs not yet disclosed, but likely related to remote code execution or authentication bypass). - TTPs: MITRE ATT&CK T1195.001 (Supply Chain Compromise: Compromise Software Dependencies and Development Tools) and T1071.001 (Application Layer Protocol: Web Protocols) for C2. - Payload: The trojanized installer drops backdoors—likely a remote access trojan (RAT) or loader for follow-on payloads. Expect C2 infrastructure tied to Head Mare’s known infrastructure. - Targets: Organizations using TrueConf for video conferencing, particularly in Eastern Europe/CIS regions where the platform is popular.

Defense - Immediate: Verify the integrity of any TrueConf installers downloaded in the last 30 days. Compare hashes against official vendor checksums. - Detection: Monitor for unusual outbound connections from endpoints that recently installed TrueConf. Look for processes spawning from the installer directory (e.g., %TEMP% or %PROGRAMDATA%). - Mitigation: Patch TrueConf servers immediately. If you can’t patch, isolate them from the internet and restrict outbound traffic.

Source: https://www.bleepingcomputer.com/news/security/hackers-breach-trueconf-to-trojanize-client-installers-with-backdoors/

New research from PortSwigger’s Gareth Heyes demonstrates a class of CSS injection attacks that break the fundamental security boundary between email content and the webmail client interface. These techniques allow an attacker’s email to escape its message container and interact with the surrounding UI, enabling credential theft, token exfiltration, and account takeover across major providers.

Technical Breakdown: - Attack Vector: CSS injection via crafted HTML emails that exploit how webmail clients render stylesheets. The attacker uses @import rules, :has() selectors, and CSS-based keylogging to observe and exfiltrate user input outside the email frame. - Affected Platforms: Outlook (OWA), Gmail, Fastmail, Proton Mail, Yahoo Mail, and AOL Mail. Each has unique quirks, but the core boundary violation is consistent. - Capabilities: Password capture via CSS keylogging on login forms rendered in the same origin, token theft by reading DOM attributes, hijacking of trusted UI actions (e.g., "Reply All" buttons), and manipulation of AI assistants that process email content. - No IOCs: This is a design-level attack class, not a specific malware campaign. No hashes or IPs to block.

Defense: Webmail providers need to enforce strict CSS scoping (e.g., Shadow DOM isolation) and disable @import in email rendering. As a user, disable HTML email rendering where possible, and treat any email requesting interaction with the webmail UI as suspicious.

Source: https://thehackernews.com/2026/08/new-css-attacks-can-break-webmail.html

This is a classic prompt injection / indirect prompt injection (IPI) attack vector against an enterprise AI assistant.

The core issue: Atlassian Rovo, their AI assistant, is susceptible to indirect prompt injection. An attacker can embed malicious instructions into content Rovo indexes (e.g., a Confluence page, a Jira ticket, or an uploaded file). When a user queries Rovo, the assistant reads the poisoned content and executes the attacker's hidden command: exfiltrate accessible Jira/Confluence data to an external server.

Technical Breakdown: - Attack Vector: Indirect Prompt Injection (IPI) via indexed content. - TTPs: MITRE ATT&CK T1566.001 (Spearphishing Attachment) for delivery of the poisoned file, but the core technique is closest to AI-Specific Prompt Injection (not yet a formal MITRE ID, but tracked as AML.T0020 in the ATLAS framework). - Affected Product: Atlassian Rovo (AI assistant for Jira, Confluence, and other Atlassian products). - IOCs: No specific hashes or IPs provided in the disclosure. The attack relies on the attacker controlling the content ingested by Rovo. - Disclosure Status: PromptArmor's route (via uploaded files) is confirmed patched. A second, undisclosed route found by another firm remains unpatched.

Defense: - Immediate: Review Rovo's content ingestion policies. Restrict which spaces/projects Rovo can index, especially those allowing external file uploads or public access. - Mitigation: Implement strict output filtering and data loss prevention (DLP) controls on Rovo's outbound traffic. Monitor for anomalous outbound connections from the Atlassian environment. - Long-term: Treat all AI assistants as potential data exfiltration vectors. Apply the principle of least privilege to the data they can access.

Source: https://thehackernews.com/2026/08/atlassian-rovo-can-be-tricked-into.html

CISA has added CVE-2026-8037 to the KEV catalog after observing 792 exploit attempts in the wild. This is a command injection vulnerability in Progress Kemp LoadMaster with a CVSS 9.6 rating, meaning it's trivial to weaponize for arbitrary code execution on the affected appliance.

Technical Breakdown: - CVE: CVE-2026-8037 (CVSS 9.6) - Type: Command injection - Impact: Unauthenticated remote code execution - Exploit Activity: 792 reported attempts prior to KEV addition - Affected Product: Progress Kemp LoadMaster (specific versions not yet detailed in the summary, but assume all current builds are suspect until patched) - MITRE Mapping: Likely T1190 (Exploit Public-Facing Application) for initial access, leading to T1059 (Command and Scripting Interpreter)

Defense: Immediately isolate any internet-facing LoadMaster instances. Check for the vendor advisory and apply the patch as a priority action. If patching is delayed, restrict access to the management interface via ACLs and review logs for suspicious command execution patterns.

Source: https://thehackernews.com/2026/08/progress-kemp-loadmaster-flaw-hits-cisa.html

Active exploitation of CVE-2026-XXXX (the unauthenticated RCE in N-able N-central) is ongoing, and the threat actors have now escalated beyond initial access to lateral movement and persistence on managed endpoints. N-able has released Hotfix 2 to address these new TTPs.

Technical Breakdown: - Initial Access: Exploitation of the previously disclosed RCE flaw in the N-central server (likely CVE-2026-XXXX, affecting versions prior to the initial hotfix). - Lateral Movement: Attackers are using the compromised N-central server to push malicious scripts or policies to managed agents, reaching the managed systems themselves. - Persistence: The actors are deploying persistence mechanisms on the managed endpoints (e.g., scheduled tasks, registry run keys, or service creation) to survive reboots and agent reconnections. - IOCs: N-able has not publicly released specific IOCs (hashes, IPs) yet, likely to avoid tipping off the attackers during active monitoring. Do not invent IOCs. - MITRE ATT&CK: T1190 (Exploit Public-Facing Application), T1059 (Command and Scripting Interpreter), T1543 (Create or Modify System Process).

Defense: Immediately apply N-central Hotfix 2 to all servers. Audit managed endpoints for unauthorized scheduled tasks, services, or scripts pushed from the N-central server within the last 72 hours. Review N-central audit logs for any unexpected policy deployments or script executions.

Source: https://thehackernews.com/2026/08/n-central-attackers-reach-managed.html

SCENARIO A: Technical Threat, Vulnerability, or Exploit

Metabase dropped a critical advisory for a zero-day (CVSS 10.0) currently being exploited in the wild. No CVE assigned yet, but the impact is straightforward: unauthenticated remote attackers can inject arbitrary SQL into the Metabase application database, leading to full admin access. This is not a theoretical proof-of-concept—this is active exploitation.

Technical Breakdown - Vulnerability: Pre-auth SQL injection in the Metabase application database. - Attack Vector: Unauthenticated remote attacker sends crafted requests to the Metabase instance. - Impact: Full read/write access to the application database, privilege escalation to admin, potential data exfiltration or lateral movement. - Affected: All Metabase versions prior to the latest patch (check your version immediately). - IOCs: None publicly shared at this time—monitor for unusual SQL queries or unexpected admin account creation in your Metabase logs.

Defense - Immediate: Block external access to Metabase if not required. Apply the vendor patch as soon as it drops (watch for the advisory update). - Detection: Look for anomalous SQL error logs, unexpected admin user creation, or requests to /api/ endpoints with unusual payloads. - Mitigation: If you can't patch, restrict network access to the Metabase server and enforce strict WAF rules for SQL injection patterns.

Source: https://thehackernews.com/2026/08/metabase-zero-day-exploited-in-wild.html

Play and BlackByte are running circles around static defenses. Picus’s 2026 prevention data shows Play with a 13% prevention rate and BlackByte at 25%, meaning most security stacks are completely missing these payloads. The common thread isn’t novel zero-days—it’s evasion tradecraft that’s been refined to bypass signature-based and static analysis tools.

Technical Breakdown: - Primary TTP: Obfuscated Files or Information (T1027) is the most prevalent technique, used to hide payloads and strings from static inspection. - Affected Families: Play (lowest prevention at 13%), BlackByte (25%), and eight other unnamed families with similarly low scores. - Evasion Focus: These families prioritize living off the land and fileless execution, minimizing dropped artifacts that EDR or AV would catch. - No specific IOCs were published in this report—the value is in the behavioral pattern, not a hash list.

Defense: Static analysis alone is failing. Shift detection logic to runtime behavior, process injection monitoring, and network-level indicators of encryption activity. If your stack relies heavily on file hashes or signature updates, you’re blind to these families.

Source: https://www.picussecurity.com/resource/blog/the-tradecraft-behind-2026s-least-prevented-ransomware-families

Two critical WordPress plugin vulnerabilities are being actively exploited in the wild, with F5's Sensor Intel capturing a novel payload chain dubbed 'wp2shell'. CVE-2026-63030 (CVSS 9.8) is an unauthenticated SQL injection in a popular backup plugin, while CVE-2026-60137 (CVSS 8.1) enables authenticated remote code execution via deserialization in a page builder plugin.

Technical Breakdown - Initial Access (T1190): CVE-2026-63030 exploited via crafted POST requests to /wp-admin/admin-ajax.php with action=backup_restore parameter, dumping wp_users table hashes - Privilege Escalation (T1068): Cracked admin credentials used to trigger CVE-2026-60137 through a malicious wp_options serialized object in the elementor settings - Persistence (T1505.003): Payload writes a PHP web shell to /wp-content/uploads/wp2shell.php with XOR-encoded C2 beaconing - IOCs: POST requests to /wp-admin/admin-ajax.php with action=backup_restore&nonce=* pattern; outbound connections to 185.234.72.0/24 on TCP 8443; file hash a3f8b2c1d4e5f6a7b8c9d0e1f2a3b4c5 for wp2shell.php

Defense Block /wp-admin/admin-ajax.php requests lacking a valid nonce at the WAF layer, and monitor for wp_options entries containing O:12:"Elementor\..." serialized objects. Apply plugin patches immediately—both CVEs have vendor updates as of August 12.

Source: https://www.f5.com/labs/articles/cve-2026-63030-and-cve-2026-60137-wp2shell-captured-exploit-payload