PHP exploitation report, November 2026: 36 of 19,422 PHP CVEs are known exploited
First monthly issue. Three PHP CVEs entered CISA KEV in October–November 2026: two PHP engine use-after-frees and a WordPress core RCE. The known-exploited set grew from 35 to 36 CVEs while the feed grew by 158. Numbers, names, fixed versions, and the highest-EPSS bugs not yet in KEV.
1. The totals, and the change since October
As of 2026-11-12 the feed holds 19,422 distinct CVEs across 21,128 (package, CVE) advisory entries: 8,791 Composer advisories, 12,329 WordPress core/plugin/theme advisories, and 8 PHP engine CVEs. 36 of the 19,422 CVEs (0.19%) are known exploited — 43 advisory entries, because a CVE such as a Drupal or Magento bug is listed once per package name.
On 2026-10-28 we published 35 known-exploited CVEs out of 19,264. Fifteen days later it is 36 out of 19,422: the feed grew by 158 CVEs and the exploited set grew by one. That ratio — roughly one in 160 new PHP CVEs turning out to be exploited — is the whole argument for ranking by exploitation. The two engine CVEs below were already in the October count; they entered KEV on 2026-10-26, two days before that post.
2. Added to CISA KEV in October–November 2026
3 PHP CVEs entered the catalog in the period. For each: what CVSS said, what exploitation data says, the fixed versions, and the phpwarden command that checks a host for it.
CVE-2026-109618— Upload-progress use-after-free and remote process-memory disclosure PHP engineAdded to KEV 2026-10-26 · published 2026-10-21 · CVSS critical 9.2 · EPSS 99.99%
Fixed in
8.2 → 8.2.35, 8.3 → 8.3.36, 8.4 → 8.4.27, 8.5 → 8.5.12· Check withphpwarden scanCVE-2026-109619— Fatal-error backtrace use-after-free and OPcache type confusion PHP engineAdded to KEV 2026-10-26 · published 2026-10-21 · CVSS critical 9.2 · EPSS 99.99%
Fixed in
8.2 → 8.2.35, 8.3 → 8.3.36, 8.4 → 8.4.27, 8.5 → 8.5.12· Check withphpwarden scanCVE-2026-119977— WordPress Core is vulnerable to Remote Code Execution in versions 4.7 through 7.1.3. This is due to predictable, web-acc WordPress coreAdded to KEV 2026-11-03 · published 2026-10-31 · CVSS high 8.1 · EPSS 1.19%
Fixed in
6.8.12, 6.9.11, 7.0.8, 7.1.4 and every older branch back to 4.7.39· Check withphpwarden wordpress /var/www/html
Two things stand out. First, the engine CVEs score 9.2 on CVSS and 99.999% on EPSS — here the two agree, and both were in KEV within five days of publication. The engine does not get exploited often (4 of 8 engine CVEs are in KEV), but when it does, it happens fast. Second, the WordPress core RCE is the opposite case: CISA confirmed in-the-wild exploitation on 2026-11-03, three days after publication, while its EPSS was still about 1%. EPSS is a model fed by observation and it lags a brand-new bug; KEV is a human confirmation and it does not. A scanner that only reads one of the two misses one of these three CVEs.
The WordPress fix is unusual: it was backported to every branch from 4.7 to 7.1, so "update core" works even on a site pinned to an old branch — but only if automatic background updates are on, which on managed hosting they often are not.
3. Severity is not threat: the 36 exploited CVEs by CVSS rating
22 of the 36 known-exploited CVEs are rated critical and 9 high. The other 5 would
not clear a "fix everything high and above" policy: 4 are rated medium — CVE-2020-11023 (6.9, components/jquery), CVE-2019-9978 (6.1, social-warfare (WordPress plugin)), CVE-2026-60137 (5.9, WordPress core), CVE-2025-35939 (5.3, craftcms/cms) — and
1 carries no CVSS at all (CVE-2020-28949 (pear/archive_tar)).
Read the other way: the feed has 1,447 CVEs scored 9.0 or higher. 22 of them (1.5%) are in KEV, and 346 (24%) have an EPSS under 1%. A critical rating is a statement about what a bug could do if someone bothered. Most of the time nobody has.
4. Watch list: highest EPSS, not in KEV
KEV is curated and lags; EPSS moves every day. These are the 10 CVEs with the highest exploitation probability of anything not in the catalog as of 2026-11-12. If one of these is in your lockfile or plugin directory, treat it like a KEV entry.
| CVE | What | Affects | Severity | EPSS |
|---|---|---|---|---|
CVE-2020-11022 | Potential XSS vulnerability in jQuery | athlon1600/youtube-downloader, components/jquery +1 | medium 6.9 | 99% |
CVE-2022-39986 | RaspAP Command Injection vulnerability | billz/raspap-webgui | critical 9.8 | 99% |
CVE-2022-24637 | Improper Privilege Management in Open Web Analytics | open-web-analytics/open-web-analytics | critical 9.8 | 99% |
CVE-2018-12613 | phpMyAdmin Improper Authentication | phpmyadmin/phpmyadmin | high 8.8 | 98% |
CVE-2023-6553 | The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and in | backup-backup (WordPress plugin) | critical 9.8 | 98% |
CVE-2022-21661 | WordPress is a free and open-source content management system written in PHP and paired with a MariaDB databas | WordPress core | high 8.0 | 98% |
CVE-2016-10045 | Remote code execution in PHPMailer | phpmailer/phpmailer | critical 9.8 | 98% |
CVE-2023-0315 | Froxlor vulnerable to Command Injection | froxlor/froxlor | high 8.8 | 98% |
CVE-2019-9194 | elFinder command injection vulnerability in the PHP connector | studio-42/elfinder | critical 9.8 | 97% |
CVE-2020-11530 | A blind SQL injection vulnerability is present in Chop Slider 3, a WordPress plugin. The vulnerability is intr | chop-slider (WordPress plugin) | critical 9.8 | 95% |
Most are old, and most are management tools or CMS cores that sit on the open internet: phpMyAdmin, elFinder,
Open Web Analytics, a Craft CMS RCE from 2023. The top entry is the 2020 jQuery XSS as bundled by
maximebf/debugbar; its sibling jQuery CVE (CVE-2020-11023) is already in KEV.
Movers: comparing feed 2026.10.31.2 with 2026.11.12.2 (twelve days apart), the largest EPSS rises among Composer and
WordPress advisories were CVE-2025-23200 (librenms/librenms stored XSS,
CVSS 4.6) from 32% to 49%, CVE-2020-36847 (Simple File List WordPress plugin
RCE, fixed in 4.2.3) from 43% to 59%, and CVE-2015-5468 (WP e-Commerce Shop
Styling traversal, no fix published) from 24% to 38%. A CVSS 4.6 bug at 49% exploitation probability is the kind of row
a severity-sorted list buries on page 40.
5. Per ecosystem
| Ecosystem | CVEs | In KEV | Share |
|---|---|---|---|
| PHP engine | 8 | 4 | 50.00% |
| Composer packages | 7,650 | 24 | 0.31% |
| WordPress plugins/themes/core | 11,796 | 8 | 0.07% |
WordPress produces the most advisories and the fewest exploited ones per advisory; Composer sits in between, with its 24 exploited CVEs concentrated in CMS cores (Drupal, Magento, Craft, October) and two dev dependencies that should never be on a production host; the PHP engine has the highest exploited share by a wide margin, on a very small base. A CVE that affects more than one ecosystem is counted in each, so the rows add to slightly more than 19,422.
Wider than KEV: 666 CVEs have an EPSS of 10% or more and 226 are at 50% or more. If your patch budget is a few hours a month, the KEV set plus the 50%+ set is a list in the low hundreds, not twenty thousand.
How to check your own hosts
Everything in this report is a flag in the feed, so the check is mechanical: scan the host and the lockfile and
look for anything marked exploited. phpwarden ranks KEV first, then EPSS, then CVSS, and its CI mode has
fail-on: exploited for exactly the 36-row list above.
Two lines, no dependencies
Offline, Apache-2.0. Works on any PHP host or project.
composer require --dev phpwarden/phpwarden # or: pip install phpwarden
vendor/bin/phpwarden scan && vendor/bin/phpwarden deps composer.lock && vendor/bin/phpwarden wordpress /var/www/html
In CI: uses: oroma-alfred/phpwarden-action@v1
with fail-on: exploited.
Method and caveats
- Data: the phpwarden feed, version 2026.11.12.2, generated 2026-11-12, built from OSV.dev, FriendsOfPHP/security-advisories and NVD (WordPress), enriched with CISA KEV and FIRST EPSS. Browse it at /advisories, sorted by exploitation risk (KEV first).
- "Known exploited" means the feed's known-exploited flag. 2 of the 36 carry no KEV date in the feed (CVE-2020-35489 Contact Form 7 and CVE-2024-28000 LiteSpeed Cache) and are therefore not counted among the period's additions.
- EPSS is a 30-day exploitation probability as of the feed date and changes daily; the movers paragraph compares two feed builds twelve days apart and is a snapshot, not a trend.
- The engine set (8 CVEs) is what the feed carried on this date. It was incomplete: the feed has carried the full engine set (145 CVEs then, from the php-src release notes) since 2026-11-12; see the correction at the top. The comparison with the October post uses that post's published figures.
- The next issue will cover December 2026 and show the delta against this one. Regenerate:
scripts/build_blog.py --only php-exploitation-report-2026-11in the phpwarden repo.