Every change, newest first

What a record said when it was published, what it says now, and the commit that changed it.

15 changes behind one line · newest firstCSV JSON RSS

PublisherPublishedChangedSourceRows

One change, in full: Product added: rapidload ai – optimize web vitals automatically named as affected from shakee93. Products named as affected in 15 CVE records. Back to the ledger

Counted changes published by Wordfence, newest first, one line per change to a CVE record, or per run of identical changes collapsed into one line.
Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin.	Kind	Record, Which record was edited, by its CVE id, or how many records one collapsed line stands on.	Vendor · product, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry.	What changed	Days to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong.
2026-04-08	Product added	CVE-2023-1334	shakee93 Wordfence	not named as affected at publication, now names rapidload ai – optimize web vitals automatically	Days to revision 1,125
2026-04-08	Product added	CVE-2023-1335	shakee93 Wordfence	not named as affected at publication, now names rapidload ai – optimize web vitals automatically	Days to revision 1,125
2026-04-08	Product added	CVE-2023-1336	shakee93 Wordfence	not named as affected at publication, now names rapidload ai – optimize web vitals automatically	Days to revision 1,125
2026-04-08	Product added	CVE-2023-1337	shakee93 Wordfence	not named as affected at publication, now names rapidload ai – optimize web vitals automatically	Days to revision 1,125
2026-04-08	Product added	CVE-2023-1341	shakee93 Wordfence	not named as affected at publication, now names rapidload ai – optimize web vitals automatically	Days to revision 1,125
2026-04-08	Product added	CVE-2023-1345	shakee93 Wordfence	not named as affected at publication, now names rapidload ai – optimize web vitals automatically	Days to revision 1,125
2026-04-08	Product added	CVE-2023-1346	shakee93 Wordfence	not named as affected at publication, now names rapidload ai – optimize web vitals automatically	Days to revision 1,125
2026-04-08	Product added	CVE-2023-1340	shakee93 Wordfence	not named as affected at publication, now names rapidload ai – optimize web vitals automatically	Days to revision 1,125
2026-04-08	Product added	CVE-2023-1342	shakee93 Wordfence	not named as affected at publication, now names rapidload ai – optimize web vitals automatically	Days to revision 1,125
2026-04-08	Product added	CVE-2023-1472	shakee93 Wordfence	not named as affected at publication, now names rapidload ai – optimize web vitals automatically	Days to revision 1,118
2026-04-08	Product added	CVE-2023-1333	shakee93 Wordfence	not named as affected at publication, now names rapidload ai – optimize web vitals automatically	Days to revision 1,125
2026-04-08	Product added	CVE-2023-1338	shakee93 Wordfence	not named as affected at publication, now names rapidload ai – optimize web vitals automatically	Days to revision 1,125
2026-04-08	Product added	CVE-2023-1339	shakee93 Wordfence	not named as affected at publication, now names rapidload ai – optimize web vitals automatically	Days to revision 1,125
2026-04-08	Product added	CVE-2023-1343	shakee93 Wordfence	not named as affected at publication, now names rapidload ai – optimize web vitals automatically	Days to revision 1,125
2026-04-08	Product added	CVE-2023-1344	shakee93 Wordfence	not named as affected at publication, now names rapidload ai – optimize web vitals automatically	Days to revision 1,125

Rows, not records: a moved fix version or an extended range counts once per record, product and release branch; an added product once per record and product; every other kind once per record or advisory. Days to revision is how long the value first stated stood: from the record's or advisory's publication, or from the day a KEV field value was first seen, to the first commit that replaced it. An addition to KEV has no earlier value and shows none.

Every kind of change

Each bar filters the ledger to that kind, and counts what it would show under the filters already on. Two units, one length scale, never a total.

To a CVE record or a KEV entry

To a GitHub advisory

Data sources and quality

Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.

A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.

The units, the refusals, the cut-offs and every source, in full →

Check my CVEs against these changes →