Skip to content

Product added

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

71 changes behind one line · newest firstCSVJSONRSS

SinceClear all
ChangedSourceRows

One change, in full: Product added: 71 products named as affected in CVE-2024-51984. The same change in 1 CVE record, across 71 products: 71 rows in all. Back to all 87 products in this change · Back to the ledger

Counted changes of "Product added" published by rapid7, 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.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 changedDays 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-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-b7520dw (china)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-b7535dw (china)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-b7640dw (asia)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-j1260wTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-j1270nTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-j1310dwTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-j1313dwTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-j1360dwTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-j1460dwTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-j4250nTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-j529nTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-j916nTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-j929n w/bTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-j973n w/bTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-j978n w/bTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-j982n w/bTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-l2535dw (china)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-l2540dw (japan)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-l2550dw (china)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-l2550dw (japan)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-l2550dw (taiwan)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-l2660dw (japan)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-t580dwTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-t583dwTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names dcp-t780dwTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names hl-l2361dnTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names hl-l5210dn (japan)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names hl-l5210dw (japan)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names hl-l6310dw (japan)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-j1260wTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-j1360dwTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-j1365dwTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-j1410dwTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-j4340dweTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-j4350dwTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-j4355dwTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-j4450nTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-j4550dwTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-j4555dwTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-j4950dnTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-j742dnTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-j742dwnTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-j903nTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-j908nTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-j943dnTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-j943dwnTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-l2700dw (asia)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-l2715dw (taiwan/korea/hong kong)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-l2740dw (japan)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-l2750dw (japan)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-l2805dw (asia)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-l2860dw (japan)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-l2880dw (japan)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-l3770cdw (japan)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-l3780cdw (japan)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-l5710dw (japan)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-l5755dw (japan)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-l6900dw (japan)Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-t580dwTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-t780dwTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names mfc-t980dwTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names pj-773Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names pt-p750wTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names pt-p950nwTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names ql-1115nwbTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names rj-3050Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names rj-3150Time to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names td-2130nsaTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names td-2135nsaTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names td-2135nwbTime to revision 286 days
2026-04-07CVE-2024-51984rapid7not named as affected at publication, now names td-2135nwbsaTime to revision 286 days

This kind is counted once per record and per product, so one record that added four products counts four times and the number of records behind these changes is smaller.

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 →