Search: “plugin security”

5 stories in the last 30d

Searchkeyword smart Sortlatest hot importance relevance

DomainAll Cyber AIWindow24h 3d 7d 30d AllIn the wild Important only Show duplicates

CategoryAll Exploit / PoC 34 Threat actor 20 Vulnerability 19 Malware 9 AI safety & security 9 Industry 8 Tools 7 Phishing & fraud 6 Research 5 AI tools & infra 4 Advisory 4 AI industry 4 Policy & legal 3 Data breach 2

SeverityAll critical 16 high 53 medium 29 low 6 info 32

WordPress Blocks High-Risk Plugin Releases With New AI-Powered Automated Security Review

WordPress.org now runs AI-powered automated security reviews on every plugin release, automatically blocking high-risk updates before distribution to millions of sites.

WordPress launched an automated security review that combines multiple AI models and Jetpack Scan during a six-hour cooldown to score each plugin release; updates above the blocking threshold are automatically held back from the WordPress.org update API. The change follows a July 28 incident where a backdoor added to a plugin with roughly 20,000 active installations was detected during cooldown and never delivered; the Plugins Team removed it 26 minutes after a Wordfence notification. Blocked developers receive an email with findings and are advised to publish a corrected version rather than await manual appeal.

GBHackersupdated Sep 11, 16:33 UTC · 5d agofirst Sep 11, 05:49 UTC · 5d agoTools 7 sources1

WordPress Adds Automated Plugin Reviews to Block High-Risk Updates Before Distribution

WordPress will automatically scan every plugin release and block high-risk updates from distribution using AI analysis plus Jetpack Scan.

WordPress announced automated security reviews for every plugin release during its cooldown period before distribution through the WordPress.org update API, combining AI models with Jetpack Scan into a security score. The system already caught a backdoor committed to a plugin with about 20,000 active installations on July 28, 2026, blocking it within 26 minutes of a Wordfence alert. Flagged patterns include missing capability checks, unsafe $wpdb queries, unserialize() on request data, and obfuscated code.

The Hacker NewsSep 14, 16:00 UTC · 2d agoTools

Claude Mythos 5 is coming to Tenable One, powering the new “Adversary View”

Tenable will integrate Anthropic's Claude Mythos 5 into Tenable One, launching Adversary View to surface exploitable vulnerability chains from scan data.

Tenable announced it is bringing Anthropic's Claude Mythos 5 into the Tenable One Exposure Management Platform, extending its Project Glasswing research work with Anthropic. The first capability, Tenable One Adversary View, will use the model's adversarial reasoning over raw scanner evidence, plugin output, live connections and low-confidence signals to identify viable vulnerability chains and ranked defensive actions. Customers will act on results through Tenable Hexa AI. Availability details for Adversary View are expected in the coming weeks; no customer deployment exists yet.

Tenable BlogSep 8, 17:21 UTC · 8d agoTools1

Wazuh and AI For Enhanced SOC Workflows

Wazuh details AI-powered SOC workflows via its AI Analyst, self-hosted Llama 3 via Ollama, and Claude 3.5 Haiku integrations.

Wazuh outlines how AI can augment SOC analysts handling high alert volumes. The Wazuh AI Analyst on Wazuh Cloud uses Amazon Bedrock and Anthropic Claude to generate scheduled security posture reports. Self-hosted options include Llama 3 with Ollama, FAISS, and LangChain for privacy-sensitive threat hunting, plus an OpenSearch Assistant integration with Claude 3.5 Haiku. This is a vendor-contributed piece describing product capabilities rather than an incident or vulnerability.

The Hacker NewsAug 21, 11:21 UTC · 26d agoTools

Homebrew 7.0.0 gets built-in GUI, better security controls

Homebrew 7.0.0 adds a built-in vulnerability scanner (brew vulns), a Homebrew advisory database, stronger sandboxing, and the BrewUI GUI.

Homebrew 7.0.0 ships a native BrewUI graphical interface for macOS 26 Tahoe and later, plus a new 'brew vulns' command that queries OSV.dev in batch to flag vulnerabilities in installed formulae, specific packages, or Brewfile dependencies. The release also introduces a Homebrew-specific OSV-format advisory database distinguishing outstanding vulnerabilities from backported fixes. Sandbox improvements block home directory access by default and separate network-enabled dependency downloads from offline installs.

BleepingComputerSep 14, 19:51 UTC · 2d agoTools1