Every change, newest first

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

17 changes · newest first · grouped by dayCSV JSON RSS

Counted changes from pickplugins, 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.
Wed 8 Apr 2026· 5 changes
2026-04-08	Affected range extended	CVE-2025-12374	pickpluginsuser verification by pickplugins Wordfence	stated at publication 2.0.39, now states 2.0.44Release branch starts at 0.bulk ×119	Time to revision 125 days
2026-04-083 commits	Product added	Show all 4 CVE records in this change: Product added: post grid named as affected from pickpluginsHide the 4 CVE records in this change: Product added: post grid named as affected from pickplugins	pickplugins Wordfence	not named as affected at publication, now names post gridBranches and original-value intervals are stated on each row.	Time to revision 603 to 671 days
2026-04-08	same kind of change as the line above	CVE-2024-1988	same vendor as the line above	same change as the line above	Time to revision 671 days
2026-04-08	same kind of change as the line above	CVE-2024-4042	same vendor as the line above	same change as the line above	Time to revision 671 days
2026-04-08	same kind of change as the line above	CVE-2024-6346	same vendor as the line above	same change as the line above	Time to revision 615 days
2026-04-08	same kind of change as the line above	CVE-2024-7588	same vendor as the line above	same change as the line above	Time to revision 603 days
Wed 1 Apr 2026· 12 changes
2026-04-01	Affected range extended	Show all 2 CVE records in this change: Affected range extended: 1.2.70 → 1.2.73 from pickpluginsHide the 2 CVE records in this change: Affected range extended: 1.2.70 → 1.2.73 from pickplugins	pickpluginsquestion answer Patchstack	stated at publication 1.2.70, now states 1.2.73Release branch starts at 0.bulk ×507	Time to revision 349 to 365 days
2026-04-01	same kind of change as the line above	CVE-2025-31810	same vendor as the line above	same change as the line aboveRelease branch starts at 0.bulk ×507	Time to revision 365 days
2026-04-01	same kind of change as the line above	CVE-2025-32647	same vendor as the line above	same change as the line aboveRelease branch starts at 0.bulk ×507	Time to revision 349 days
2026-04-012 commits	Affected range extended	Show all 4 CVE records in this change: Affected range extended: 2.1.60 → 2.1.61 from pickpluginsHide the 4 CVE records in this change: Affected range extended: 2.1.60 → 2.1.61 from pickplugins	pickpluginsjob board manager Patchstack	stated at publication 2.1.60, now states 2.1.61Branches and original-value intervals are stated on each row.bulk ×507	Time to revision 355 to 471 days
2026-04-01	same kind of change as the line above	CVE-2025-31862	same vendor as the line above	same change as the line aboveRelease branch starts at 0.bulk ×507	Time to revision 365 days
2026-04-01	same kind of change as the line above	CVE-2025-32144	same vendor as the line above	same change as the line aboveRelease branch starts at 0.bulk ×507	Time to revision 355 days
2026-04-01	same kind of change as the line above	CVE-2024-55993	same vendor as the line above	same change as the line aboveRelease branch starts at 0.bulk ×86	Time to revision 471 days
2026-04-01	same kind of change as the line above	CVE-2025-22679	same vendor as the line above	same change as the line aboveRelease branch starts at 0.bulk ×86	Time to revision 422 days
2026-04-01	Affected range extended	CVE-2025-32272	pickpluginswishlist Patchstack	stated at publication 1.0.44, now states 1.0.46Release branch starts at 0.bulk ×507	Time to revision 362 days
2026-04-01	Affected range extended	CVE-2025-32143	pickpluginsaccordion Patchstack	stated at publication 2.3.10, now states 2.3.11Release branch starts at 0.bulk ×507	Time to revision 355 days
2026-04-01	Affected range extended	CVE-2025-32618	pickpluginswishlist Patchstack	stated at publication 1.0.43, now states 1.0.46Release branch starts at 0.bulk ×507	Time to revision 355 days
2026-04-01	Affected range extended	CVE-2025-58678	pickpluginsaccordion Patchstack	stated at publication 2.3.14, now states 2.3.15Release branch starts at 0.bulk ×507	Time to revision 191 days
2026-04-01	Affected range extended	CVE-2025-63043	pickpluginspost grid and gutenberg blocks Patchstack	stated at publication 2.3.19, now states 2.3.23Release branch starts at 0.bulk ×507	Time to revision 104 days
2026-04-01	Affected range extended	CVE-2024-53772	pickpluginsmail picker Patchstack	stated at publication 1.0.14, now states 1.0.15Release branch starts at 0.bulk ×86	Time to revision 487 days

Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

4,561 record edits in the 52 weeks to 2026-09-07. Scroll for earlier dates.fewermore

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

What this page cannot see

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 →

Paste your closed CVE tickets and see which of these changes hit them →