Affected range extended
| 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 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· 1 record change | ||||
| 2026-04-08 | 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 | Days to revision 125 |
| Wed 1 Apr 2026· 12 record changes | ||||
| 2026-04-01 | CVE-2025-31810 | pickpluginsquestion answer Patchstack | stated at publication 1.2.70, now states 1.2.73Release branch starts at 0.bulk ×507 | Days to revision 365 |
| 2026-04-01 | CVE-2025-31862 | pickpluginsjob board manager Patchstack | stated at publication 2.1.60, now states 2.1.61Release branch starts at 0.bulk ×507 | Days to revision 365 |
| 2026-04-01 | CVE-2025-32272 | pickpluginswishlist Patchstack | stated at publication 1.0.44, now states 1.0.46Release branch starts at 0.bulk ×507 | Days to revision 362 |
| 2026-04-01 | CVE-2025-32143 | pickpluginsaccordion Patchstack | stated at publication 2.3.10, now states 2.3.11Release branch starts at 0.bulk ×507 | Days to revision 355 |
| 2026-04-01 | CVE-2025-32144 | pickpluginsjob board manager Patchstack | stated at publication 2.1.60, now states 2.1.61Release branch starts at 0.bulk ×507 | Days to revision 355 |
| 2026-04-01 | CVE-2025-32618 | pickpluginswishlist Patchstack | stated at publication 1.0.43, now states 1.0.46Release branch starts at 0.bulk ×507 | Days to revision 355 |
| 2026-04-01 | CVE-2025-32647 | pickpluginsquestion answer Patchstack | stated at publication 1.2.70, now states 1.2.73Release branch starts at 0.bulk ×507 | Days to revision 349 |
| 2026-04-01 | CVE-2025-58678 | pickpluginsaccordion Patchstack | stated at publication 2.3.14, now states 2.3.15Release branch starts at 0.bulk ×507 | Days to revision 191 |
| 2026-04-01 | 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 | Days to revision 104 |
| 2026-04-01 | CVE-2024-53772 | pickpluginsmail picker Patchstack | stated at publication 1.0.14, now states 1.0.15Release branch starts at 0.bulk ×86 | Days to revision 487 |
| 2026-04-01 | CVE-2024-55993 | pickpluginsjob board manager Patchstack | stated at publication 2.1.60, now states 2.1.61Release branch starts at 0.bulk ×86 | Days to revision 471 |
| 2026-04-01 | CVE-2025-22679 | pickpluginsjob board manager Patchstack | stated at publication 2.1.60, now states 2.1.61Release branch starts at 0.bulk ×86 | Days to revision 422 |
This kind is counted once per record, product and release branch, so one record that moved the boundary on four branches counts four times and the number of records behind these changes is smaller. 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.
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 →