phpwarden

Exploited-vulnerability coverage commitment

What phpwarden promises about known-exploited PHP vulnerabilities, how the promise is checked, and where to see the evidence. Last updated 2026-11-13.

The commitment

When CISA adds a vulnerability to its Known Exploited Vulnerabilities (KEV) catalogue and it is in phpwarden's scope, it is in the maintained feed, marked as known exploited, within 24 hours of CISA listing it.

In scope means one of three things: the PHP engine itself, a Composer package published on Packagist, or WordPress core, a plugin or a theme.

The free weekly channel does not wait for its weekly refresh in this case. A rebuild that adds a known-exploited entry the free snapshot lacks releases a new free snapshot in the same run.

How it is checked

The feed is rebuilt twice a day. Every rebuild downloads the current CISA catalogue, finds every entry whose vendor or product is PHP-related, and compares that list with the feed. Anything in scope that the feed does not have is a gap. The rebuild logs it and writes it to a public status file.

The public status file

https://phpwarden.io/feeds/kev-status.json is replaced on every rebuild. You can check it yourself or point a monitor at it.

FieldMeaning
checkedWhen this comparison ran (UTC).
feed_versionThe feed build the comparison belongs to.
kev_catalog_version, kev_entries_totalWhich CISA catalogue was read, and how many entries it has.
kev_php_relatedHow many of those entries name a PHP-related vendor or product.
kev_php_related_in_feedHow many of them are in the feed.
gapsIn-scope entries from the last 365 days that the feed lacks, each with the CVE, product, the date CISA listed it and the hours since. Empty when there is nothing missing.
sla_hours, sla_metThe commitment (24) and whether it holds. sla_met is false as soon as any gap is more than 24 hours old, counted from the start of the listing day in UTC.
out_of_scopePHP-related entries deliberately not covered, each with the reason.
scopeThe scope statement above.

What is out of scope, and why

Some KEV entries mention PHP software that phpwarden cannot match against anything it scans. They are listed in the open repository (feedbuilder/kev-out-of-scope.json) and in the status file, so the gap count only shows real gaps.

CVEWhy it is not covered
CVE-2026-56290Joomla extension (Joomlack Page Builder): Joomla is not distributed through Composer
CVE-2026-48907Joomla extension (Joomla Content Editor): Joomla is not distributed through Composer
CVE-2026-41940cPanel & WHM / WP2 (WordPress Squared): a hosting control panel product, not WordPress or a plugin
CVE-2023-23752Joomla core: Joomla is not distributed through Composer
CVE-2019-16759vBulletin: commercial forum software, not distributed through Composer
CVE-2020-17496vBulletin: commercial forum software, not distributed through Composer

Joomla core and its extensions are not installed through Composer, vBulletin is commercial software, and cPanel is a hosting control panel. If phpwarden gains a way to detect one of these, it moves into scope and off this list.

When it is missed

The status file shows sla_met: false and names the CVE. The fix is a hand-written entry in the feed's curated base file with the affected and fixed versions from the vendor's advisory, shipped in the next rebuild. Nothing is hidden or back-dated: the file reports what the comparison found at the time it ran.

History

13 November 2026. A check against the CISA catalogue found in-scope entries missing from the feed: 5 from the previous twelve months (three in Adobe Commerce / Magento Open Source, one in WordPress core, one in Roundcube) and 13 older ones (nine in Roundcube, two in ThinkPHP, one in phpMyAdmin, one in PHP-CGI). The cause was the same each time: no upstream source had linked the CVE to a package, so it never entered the feed. All 18 were added by hand that day, and the automated comparison and this status file were introduced the same day. Before that date there was no such check.

What this is not