Every change, newest first

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

14 changes behind one line · newest firstCSV JSON RSS

One change, in full: Product added: 4 products named as affected from saadiqbal. The same change in 14 CVE records, across 4 products. Drawn here as 4 lines, one per product. Back to the ledger

Counted changes from saadiqbal, 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-083 commits	Product added	Show all 8 CVE records in this change: Product added: post smtp – complete email deliverability and smtp solution with email logs, alerts, backup smtp & mobile app named as affected from saadiqbalHide the 8 CVE records in this change: Product added: post smtp – complete email deliverability and smtp solution with email logs, alerts, backup smtp & mobile app named as affected from saadiqbal	saadiqbal Wordfence	not named as affected at publication, now names post smtp – complete email deliverability and smtp solution with email logs, alerts, backup smtp & mobile appBranches and original-value intervals are stated on each row.	Time to revision 217 to 1,002 days
2026-04-08	same kind of change as the line above	CVE-2023-6875	same vendor as the line above	same change as the line above	Time to revision 818 days
2026-04-08	same kind of change as the line above	CVE-2023-3082	same vendor as the line above	same change as the line above	Time to revision 1,002 days
2026-04-08	same kind of change as the line above	CVE-2023-6629	same vendor as the line above	same change as the line above	Time to revision 827 days
2026-04-08	same kind of change as the line above	CVE-2023-7027	same vendor as the line above	same change as the line above	Time to revision 827 days
2026-04-08	same kind of change as the line above	CVE-2025-0521	same vendor as the line above	same change as the line above	Time to revision 414 days
2026-04-08	same kind of change as the line above	CVE-2025-9219	same vendor as the line above	same change as the line above	Time to revision 217 days
2026-04-08	same kind of change as the line above	CVE-2024-13844	same vendor as the line above	same change as the line above	Time to revision 397 days
2026-04-08	same kind of change as the line above	CVE-2024-5207	same vendor as the line above	same change as the line above	Time to revision 679 days
2026-04-08	Product added	Show all 2 CVE records in this change: Product added: password protected — lock entire site, pages, posts, categories, and partial content named as affected from saadiqbalHide the 2 CVE records in this change: Product added: password protected — lock entire site, pages, posts, categories, and partial content named as affected from saadiqbal	saadiqbal Wordfence	not named as affected at publication, now names password protected — lock entire site, pages, posts, categories, and partial content	Time to revision 694 to 778 days
2026-04-08	same kind of change as the line above	CVE-2024-0437	same vendor as the line above	same change as the line above	Time to revision 694 days
2026-04-08	same kind of change as the line above	CVE-2024-0656	same vendor as the line above	same change as the line above	Time to revision 778 days
2026-04-08	Product added	CVE-2024-5861	saadiqbal Wordfence	not named as affected at publication, now names wp easy pay – payment and donation form builder for square	Time to revision 624 days
2026-04-08	Product added	Show all 3 CVE records in this change: Product added: points management system for gamification, ranks, badges, and loyalty rewards program – mycred named as affected from saadiqbalHide the 3 CVE records in this change: Product added: points management system for gamification, ranks, badges, and loyalty rewards program – mycred named as affected from saadiqbal	saadiqbal Wordfence	not named as affected at publication, now names points management system for gamification, ranks, badges, and loyalty rewards program – mycred	Time to revision 489 to 561 days
2026-04-08	same kind of change as the line above	CVE-2024-10187	same vendor as the line above	same change as the line above	Time to revision 516 days
2026-04-08	same kind of change as the line above	CVE-2024-11201	same vendor as the line above	same change as the line above	Time to revision 489 days
2026-04-08	same kind of change as the line above	CVE-2024-8658	same vendor as the line above	same change as the line above	Time to revision 561 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.

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 →