Skip to content

Get notified

Get an email when a new major security incident drops. No spam, unsubscribe any time.

Only used for pwn.watch incident emails. Protected by Cloudflare Turnstile.

// tag

PHP

PHP, plus apps and CMSs built on it (WordPress, Drupal, Joomla, Magento). Newest first.

incidents
10
live
1
patched
8
rss json llms.txtall tags

## 10 PHP incidents in the last year

through Oct 22, 2026
crit 4 · high 3 · med 2 · low 1 · upd ½lessmore
  • highclosedpartial fixclosed Oct 20, 2026

    TeamUpdraft / UpdraftCentral keys stolen; WordPress sites backdoored

    › UpdraftPlus / UpdraftCentral (WordPress)

    UK plugin maker TeamUpdraft said attackers breached its website, stole UpdraftCentral connection keys, and used them to backdoor WordPress sites running UpdraftPlus/UpdraftCentral.

  • criticallivepartial fixsince Oct 17, 2026

    PHP2Shell: critical unauthenticated RCE in PHP core

    › PHP

    Two critical remote-code-execution flaws in PHP core (CVE-2026-109618 and CVE-2026-109619, aka “PHP2Shell”) were disclosed early after an embargo leak. Both score CVSS 9.2 and can let an unauthenticated attacker run code on servers serving PHP web requests, especially Apache mod_php. Patches shipped Oct 21 2026 (appliance vendors such as QNAP are still preparing fixes); exploitation attempts were observed before and after the patch, and watchTowr / AWS report active scanning.

    CVE-2026-109618CVE-2026-109619
  • criticalclosedpatchedclosed Oct 16, 2026

    Rank Math PRO WordPress plugin download backdoored

    › Rank Math PRO (WordPress)

    SEO plugin vendor Rank Math confirmed attackers tampered with PRO version 3.0.123 on the official download site, planting hidden backdoors during an ~11-hour window. Sites that installed that build should audit and rebuild.

  • highWordPress Core: WordPress Core Remote File Inclusion Vulnerability

    › WordPress Core patched

    WordPress Core contains a remote file inclusion vulnerability which could allow an unauthenticated attacker to make page-template resolution include a chosen readable local `.php` file outside the active theme directories, leading to remote code execution. Added to CISA KEV on 2026-09-25.

    open incident →CVE-2026-87902
  • highAdobe Commerce and Magento : Adobe Commerce and Magento Incorrect Authorization Vulnerability

    › Adobe Commerce and Magento patched

    Adobe Commerce and Magento contains an incorrect authorization vulnerability that could allow an attacker to leverage this vulnerability to gain elevated access to sensitive resources without any user interaction. Added to CISA KEV on 2026-09-24.

    open incident →CVE-2026-71362
show 5 older incidents

September 2026 1

  • highAdobe Commerce and Magento: Adobe Commerce and Magento Improper Neutralization of Special Elements Used in a Template Engine Vulnerability

    › Adobe Commerce and Magento patched

    Adobe Commerce and Magento Open Source contain an improper neutralization of special elements used in a template engine vulnerability that could allow an attacker to execute arbitrary code. Added to CISA KEV on 2026-09-08.

    open incident →CVE-2026-75650

July 2026 2

  • highWordPress Core: WordPress Core SQL Injection Vulnerability

    › WordPress Core patched

    WordPress Core contains a SQL injection vulnerability when a plugin or theme passes untrusted input to the parameter. This vulnerability can be chained with CVE-2026-63030 to allow an unauthenticated attacker to gain remote code execution on default WordPress installations. CISA added CVE-2026-60137, CVE-2026-63030 to the Known Exploited Vulnerabilities catalog on 2026-07-21 based on evidence of active exploitation.

    open incident →CVE-2026-60137 · CVE-2026-63030
  • highJoomlack Page Builder: Joomlack Page Builder Improper Access Control Vulnerability

    › Joomlack Page Builder patched

    Joomlack Page Builder contains an improper access control vulnerability that could allow for remote code execution via unauthenticated arbitrary file upload. Added to CISA KEV on 2026-07-07.

    open incident →CVE-2026-56290

June 2026 1

  • highWidget Factory Joomla Content Editor : Widget Factory Joomla Content Editor Improper Access Control Vulnerability

    › Widget Factory Joomla Content Editor patched

    Widget Factory Joomla Content Editor contains an improper access control vulnerability which could allow for upload and execution of PHP code via the creation of new editor profiles for unauthenticated users. Added to CISA KEV on 2026-06-16.

    open incident →CVE-2026-48907

May 2026 1

  • highDrupal Core: Drupal Core SQL Injection Vulnerability

    › Drupal Core patched

    Drupal Core contains a SQL injection vulnerability that could allow for privilege escalation and remote code execution via specially crafted requests sent with the database abstraction API. Added to CISA KEV on 2026-05-22.

    open incident →CVE-2026-9082

## posts 12

  • › PHP2Shell: critical unauthenticated RCE in PHP core
    Zed Attack Proxy
    @zaproxy

    Blog: Detecting PHP2Shell and Other PHP Vulnerabilities with ZAP PHP2Shell is the latest big “named” vulnerability. ZAP can now tell you if a site is running a vulnerable version of PHP, and it does so without sending a single extra request. t.co/9G4DtEhMM6 #php2shell

  • › PHP2Shell: critical unauthenticated RCE in PHP core
    George Kurtz
    @George_Kurtz

    #PHP2Shell is a big one. Here are my takeaways. 1. These flaws reach back more than a decade. PHP’s maintainers identified one underlying problem in 2024, but its full impact wasn’t clear until AI-assisted research demonstrated its exploitability. What seems impractical to exploit today could easily be exploitable tomorrow as models advance. 2. Much of the web runs on PHP, and a lot of it is on versions that are out of support. Some get a source backport you must build yourself. Some get nothing. Attackers aren't hunting the servers you just patched. They're hunting the ones you forgot you own. There is going to be a very long tail on remediating these vulnerabilities, and we will see many downstream breaches over the coming months. 3. The patching window has completely collapsed. While we’ve exponentially found more vulnerabilities and exponentially created more patches, we’ve hit the sound barrier on operationally rolling them out. Even more concerning is the increase in exploitation occurring before or on the day of disclosure. When a flaw gets exploited, almost 90% of the time it’s hit on or before the day it’s disclosed. As defenders, you need to be looking at your watch, not a calendar! 4. Coordinated disclosure in open source is really hard. It runs on trust, not contracts. There were many people in the loop, and for good reason. Lots of great people doing incredible work. However, I expect leaked disclosures will be the norm, not the exception, as we move forward in the Agent-state era. The @a16z chart below says it all.

  • › PHP2Shell: critical unauthenticated RCE in PHP core
    Appwrite
    @appwrite

    An update on PHP2Shell and the eMudhra certificate compromise. We've confirmed that Appwrite is not affected by PHP2Shell. Appwrite Cloud is also patched for eMudhra in every region. Here's what we've checked and what self-hosted users should do. 🧵

  • › PHP2Shell: critical unauthenticated RCE in PHP core
    ピクシブ株式会社 pixiv Inc.
    @pixiv_corp

    【#pixiv_inside】 PHP 8.5.12の緊急リリースに pixivはどう対応したか t.co/zYpXH9HWOy PHPにて緊急セキュリティリリースが予告され pixivも対応しました。 セキュリティアップデート公開から pixivメンテナンス明けまで約30分の対応を ビルド・デプロイ基盤も踏まえながら説明します✍️

  • › PHP2Shell: critical unauthenticated RCE in PHP core
    Werner Vogels
    @Werner

    Using AWS WAF to apply mitigations for PHP2Shell RCE vulnerabilities (CVE-2026-109618 and CVE-2026-109619) t.co/TW2zDAFV6K

  • › PHP2Shell: critical unauthenticated RCE in PHP core
    Matthew Prince 🌥
    @eastdakota

    Two classes extremely bad cyber vulnerabilities disclosed in the last 24 hours. The first potentially impacts everyone online. The second impacts nearly everyone running a server. tl;dr: Everyone should upgrade their OS and Browser as soon as possible. If you run a server you should upgrade PHP (or ensure it’s removed if you’re not using it) as soon as possible.

+6 more on the incident pages above.