Skip to content

Affected range extended

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

512 changes refused · newest first · grouped by dayCSVJSONRSS

SinceClear the filter
ChangedSourceRows

These rows are not counted anywhere on this site. Checked and refused means we compared this change and then rejected it: the false positive filter for this kind of change judged it to be a false positive rather than a real change. The row is shown so you can check the filter and disagree with us, and it is counted in no figure on this site. No advisory change is here: the advisory engine counts the 2,291 version pairs its filters refused by class rather than writing them out one by one, so this view holds CVE and KEV changes only.

Rows we checked and refused, counted nowhere of "Affected range extended", 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.
Wed 1 Apr 2026· 21 record changes
2026-04-01CVE-2025-32193
wpmindssimple wp events
Patchstack
stated at publication 1.8.17, now states 1.9.0Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 1.8.17 still holdsnot dated
2026-04-01CVE-2025-32195Patchstackstated at publication 7.0, now states 7.0.1Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0 still holdsnot dated
2026-04-01CVE-2025-32199
eyale-vccontact form builder by vcita
Patchstack
stated at publication 4.10.2, now states 4.10.5Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 4.10.2 still holdsnot dated
2026-04-01CVE-2025-32202
brian batt - elearningfreak.cominsert or embed articulate content into wordpress
Patchstack
stated at publication 4.3000000025, now states 4.3000000026Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 4.3000000025 still holdsnot dated
2026-04-01CVE-2025-32553
magnigenierestropress
Patchstack
stated at publication 3.1.8.4, now states 3.2.8.4Release branch starts at 0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 355
2026-04-01CVE-2025-32595
gaviaskrowd
Patchstack
stated at publication 1.4.1, now states 1.5.0Release branch starts at 0.Not counted: Same claim, other operator. `<= 1.5.0` is stated beside a fix at 1.5.0, which together say `< 1.5.0` — the next release after 1.4.1, the same claim under the other operatorDays to revision 296
2026-04-01CVE-2025-32669
mergadomergado pack
Patchstack
stated at publication 4.1.1, now states 4.2.1Release branch starts at 0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 357
2026-04-01CVE-2025-47579
themegoodsphotography
Patchstack
stated at publication 7.5.2, now states 7.7.2Release branch starts at 0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 204
2026-04-01CVE-2025-48114
shayan farhang pazhoohshayanweb admin fontchanger
Patchstack
stated at publication 1.8.1, now states 1.9.1Release branch starts at 0.Original value first replaced 2025-09-15; this value first seen 2026-04-01.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 122
2026-04-01CVE-2025-48147
crypto cloudcryptocloud - crypto payment gateway
Patchstack
stated at publication 2.1.2, now states 2.3.2Release branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2026-04-01CVE-2025-53330
wpestatewp rentals
Patchstack
stated at publication 3.13.1, now states 3.16.1Release branch starts at 0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 230
2026-04-01CVE-2025-53334
tielabsjannah
Patchstack
stated at publication 7.4.1, now states 7.5.1Release branch starts at 0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 216
2026-04-01CVE-2025-60100
8themexstore
Patchstack
stated at publication 9.5.3, now states 9.6Release branch starts at 0.Not counted: Same claim, other operator. `<= 9.6` is stated beside a fix at 9.6, which together say `< 9.6` — the next release after 9.5.3, the same claim under the other operatorDays to revision 187
2026-04-01CVE-2025-60112
syed balkhiathemes addons for elementor
Patchstack
stated at publication 1.1.3, now states 1.1.3Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `unaffected_start` on the same or the next release — the same claim under the other operatorDays to revision 187
2026-04-01CVE-2025-60116
themegoodsgrand conference theme custom post type
Patchstack
stated at publication 2.6.3, now states 2.6.4Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `unaffected_start` on the same or the next release — the same claim under the other operatorDays to revision 187
2026-04-01CVE-2024-44064
likebtnlike button rating
Patchstack
stated at publication 2.6.54, now states 2.6.54Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `unaffected_start` on the same or the next release — the same claim under the other operatorDays to revision 561
2026-04-01CVE-2024-54212
noor alammagical addons for elementor
Patchstack
stated at publication 1.2.6, now states 1.3.6Release branch starts at 0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 481
2026-04-01CVE-2024-54260
blazethemesnews kit elementor addons
Patchstack
stated at publication 1.2.2, now states 1.4.2Release branch starts at 0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 478
2026-04-01CVE-2024-54261
hk digital agency llctax service electronic hdm
Patchstack
stated at publication 1.1.2, now states 1.2.2Release branch starts at 0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 474
2026-04-01CVE-2024-56231
debuggers studiosaaspricing
Patchstack
stated at publication 1.1.4, now states 1.2.4Release branch starts at 0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 456
2026-04-01CVE-2025-22636Patchstackstated at publication 3.0.1, now states 4.0.1Release branch starts at 0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 349
Wed 11 Mar 2026· 1 record change
2026-03-11CVE-2025-40926
kazeburoplack::middleware::session::simple
CPANSec
stated at publication 0.04, now states 0.05Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 7
Tue 10 Mar 2026· 3 record changes
2026-03-10CVE-2026-2741
vaadinflow
stated at publication 24.9.8, now states 24.9.9Release branch starts at 24.0.0.Not counted: Description already named the later value. the record's own description at publication already named 24.9.9 — the structured field was corrected to the value the prose stated, not a fix that movedDays to revision 0
2026-03-10CVE-2026-2741
vaadinflow
stated at publication 25.0.2, now states 25.0.3Release branch starts at 25.0.0.Not counted: Description already named the later value. the record's own description at publication already named 25.0.3 — the structured field was corrected to the value the prose stated, not a fix that movedDays to revision 0
2026-03-10CVE-2026-2742
vaadinflow
stated at publication 25.0.1, now states 25.0.1Release branch starts at 25.0.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
Fri 6 Mar 2026· 1 record change
2026-03-06CVE-2025-1394
silabs.comzigbee stack
Silabs
stated at publication 4.3.4, now states 4.4.4Release branch starts at 0.Original value first replaced 2025-08-08; this value first seen 2026-03-06.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 9
Fri 27 Feb 2026· 1 record change
2026-02-27CVE-2025-15579
opentext™directory services
stated at publication 26.1, now states 26.1.2Release branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matchednot dated
Wed 11 Feb 2026· 1 record change
2026-02-11CVE-2025-11468PSFstated at publication 3.15.0, now states 3.15.0a6Release branch starts at 0.Original value first replaced 2026-01-20; this value first seen 2026-02-11.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
Tue 27 Jan 2026· 1 record change
2026-01-27CVE-2024-50571
fortinetfortianalyzer
stated at publication 7.2.8, now states 7.2.9Release branch starts at 7.2.0.Not counted: Description already named the later value. the record's own description at publication already named 7.2.9 — the structured field was corrected to the value the prose stated, not a fix that movedDays to revision 105
Wed 21 Jan 2026· 1 record change
2026-01-21CVE-2025-59870
hcl softwaremyxalytics
HCL
stated at publication 6.7, now states 6.7Release branch starts at 6.2.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 5
Thu 15 Jan 2026· 1 record change
2026-01-15CVE-2026-22200
enhancesoftosticket
VulnCheck
stated at publication 1.18.2, now states 1.18.3Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 3
Wed 31 Dec 2025· 1 record change
2025-12-31CVE-2025-68973
gnupggnupg
mitre
stated at publication 2.4.8, now states 2.4.9Release branch starts at 0.Original value first replaced 2025-12-29; this value first seen 2025-12-31.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 1
Tue 16 Dec 2025· 2 record changes
2025-12-16PSFstated at publication 3.15.0, now states 3.15.0a3Release branch starts at 0.Original value first replaced 2025-12-01; this value first seen 2025-12-16.not counted: Same claim, other operatorDays to revision 0
2025-12-16CVE-2025-13836same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Original value first replaced 2025-12-01; this value first seen 2025-12-16.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
2025-12-16CVE-2025-13837same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Original value first replaced 2025-12-01; this value first seen 2025-12-16.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
Mon 15 Dec 2025· 3 record changes
2025-12-15VulnCheckstated at publication 14.12.0.304, now states 14.12.0001Release branch starts at 0.not counted: Same claim, other operatorDays to revision 0
2025-12-15CVE-2025-34179same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
2025-12-15CVE-2025-34180same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
2025-12-15CVE-2025-34181same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
Tue 2 Dec 2025· 1 record change
2025-12-02CVE-2025-6075PSFstated at publication 3.14.0, now states 3.14.1Release branch starts at 0.Original value first replaced 2025-10-31; this value first seen 2025-12-02.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
Wed 26 Nov 2025· 1 record change
2025-11-26CVE-2025-11411
nlnet labsunbound
stated at publication 1.24.0, now states 1.24.1Release branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 1.24.1 — the structured field was corrected to the value the prose stated, not a fix that movedDays to revision 35
Tue 4 Nov 2025· 1 record change
2025-11-04CVE-2025-3248
langflow-ailangflow
VulnCheck
stated at publication 1.2.0, now states 1.3.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 211
Mon 27 Oct 2025· 1 record change
2025-10-27CVE-2025-30950
wp whamall currencies for woocommerce
Patchstack
stated at publication 2.4.4, now states 2.4.4Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `unaffected_start` on the same or the next release — the same claim under the other operatorDays to revision 143
Thu 16 Oct 2025· 1 record change
2025-10-16CVE-2025-2905
wso2wso2 api manager
stated at publication 2.0.0, now states 2.0.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 164
Thu 9 Oct 2025· 1 record change
2025-10-09CVE-2025-8291PSFstated at publication 3.14.0, now states 3.14.1Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 2
Fri 19 Sep 2025· 1 record change
2025-09-19CVE-2025-2404TR-CERTstated at publication 20250916, now states 20250916Release branch starts at 2.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 3
Thu 4 Sep 2025· 1 record change
2025-09-04CVE-2025-58458
jenkins projectjenkins git client plugin
jenkins
stated at publication 6.3.2, now states 6.3.3Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `unaffected_start` on the same or the next release — the same claim under the other operatorDays to revision 1
Thu 7 Aug 2025· 1 record change
2025-08-07CVE-2025-8194PSFstated at publication 3.13.5, now states 3.13.6Release branch starts at 0.Original value first replaced 2025-07-28; this value first seen 2025-08-07.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
Fri 4 Jul 2025· 1 record change
2025-07-04CVE-2025-25265
wagopfc200 g1 750-820x-xxx-xxx
CERTVDE
stated at publication 3.10.11 (FW22 Patch 2), now states 3.10.11 (FW22 Patch 2)Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 18
Thu 3 Jul 2025· 1 record change
2025-07-03CVE-2025-6587
dockerdocker desktop
stated at publication 4.42.1, now states 4.43.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
Mon 9 Jun 2025· 1 record change
2025-06-09CVE-2025-39472
wpwebwoocommerce social login
Patchstack
stated at publication 2.8.2, now states 2.8.3Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `unaffected_start` on the same or the next release — the same claim under the other operatorDays to revision 54
Thu 29 May 2025· 1 record change
2025-05-29CVE-2025-39407
caseproof, llcmemberpress
Patchstack
stated at publication 1.11.37, now states 1.12.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 10
Fri 23 May 2025· 1 record change
2025-05-23CVE-2025-48708
artifexghostscript
mitre
stated at publication 10.05.0, now states 10.05.1Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 1
Thu 15 May 2025· 1 record change
2025-05-15CVE-2025-47885
jenkins projectjenkins health advisor by cloudbees plugin
jenkins
stated at publication 358.v58972d19b_1f0, now states 374.v194b_d4f0c8c8Release branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 374.v194b_d4f0c8c8 — the structured field was corrected to the value the prose stated, not a fix that movedDays to revision 1
Wed 30 Apr 2025· 6 record changes
2025-04-30
nodejsnode
hackerone
stated at publication 22.4.0, now states 22.4.1Release branch starts at *.not counted: Release branches rewrittennot dated
2025-04-30CVE-2024-36137same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matchednot dated
2025-04-30CVE-2024-36138same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matchednot dated
2025-04-30CVE-2024-37372same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matchednot dated
2025-04-30
nodejsnode
hackerone
stated at publication 23.6.0, now states 23.6.1Release branch starts at *.not counted: Release branches rewrittennot dated
2025-04-30CVE-2025-23083same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matchednot dated
2025-04-30CVE-2025-23084same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matchednot dated
2025-04-30CVE-2025-23085same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matchednot dated
Mon 21 Apr 2025· 1 record change
2025-04-21CVE-2025-27086
hewlett packard enterprisehpe performance cluster manager (hpcm)
hpe
stated at publication 1.12, now states 1.13Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
Fri 28 Mar 2025· 1 record change
2025-03-28CVE-2025-1860
zeframdata::entropy
CPANSec
stated at publication 0.007, now states 0.008Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
Mon 24 Mar 2025· 1 record change
2025-03-24CVE-2024-13496
rubengcgamipress – gamification plugin to reward points, achievements, badges & ranks in wordpress
Wordfence
stated at publication 7.2.1, now states 7.3.1Release branch starts at 0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 61
Mon 3 Mar 2025· 1 record change
2025-03-03CVE-2025-24633
silverplugins217build private store for woocommerce
Patchstack
stated at publication 1.0, now states 1.1Release branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matchednot dated
Tue 25 Feb 2025· 31 record changes
2025-02-25
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.not counted: Prerelease named as the boundaryDays to revision 14
2025-02-25CVE-2025-24406same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24407same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24408same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24409same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24410same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24411same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24412same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24413same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
23 more rows in this change are not listed here. Open all 31 rows
Tue 28 Jan 2025· 3 record changes
2025-01-28CVE-2024-37008
autodeskrevit
stated at publication 2022.1.6, now states 2022.1.7Release branch starts at 2022.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 160
2025-01-28CVE-2024-37008
autodeskrevit
stated at publication 2023.1.4, now states 2023.1.5Release branch starts at 2023.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 160
2025-01-28CVE-2024-37008
autodeskrevit
stated at publication 2024.2.1, now states 2024.2.2Release branch starts at 2024.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 160
Fri 6 Dec 2024· 1 record change
2024-12-06CVE-2024-9287PSFstated at publication 3.13.0, now states 3.13.1Release branch starts at 0.Original value first replaced 2024-12-03; this value first seen 2024-12-06.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 42
Tue 26 Nov 2024· 1 record change
2024-11-26CVE-2024-7882TR-CERTstated at publication 22.11.2024, now states 22.11.2024Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 4
Fri 15 Nov 2024· 1 record change
2024-11-15CVE-2024-10921
mongodb incmongodb server
mongodb
stated at publication 8.0.3, now states 8.0.3Release branch starts at 8.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 1
Thu 26 Sep 2024· 2 record changes
2024-09-26
papercutpapercut ng, papercut mf
stated at publication 23.0.8, now states 23.0.9Release branch starts at 0.not counted: Same claim, other operatorDays to revision 135
2024-09-26CVE-2024-3037same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 135
2024-09-26CVE-2024-4712same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 135
Sat 7 Sep 2024· 3 record changes
2024-09-07CVE-2024-6923PSFstated at publication 3.13.0rc2, now states 3.13.0rc2Release branch starts at 0.Original value first replaced 2024-08-07; this value first seen 2024-09-07.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 6
2024-09-07PSFstated at publication 3.13.0, now states 3.13.0rc2Release branch starts at 0.not counted: Same claim, other operatorDays to revision 15 to 18
2024-09-07CVE-2024-7592same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 18
2024-09-07CVE-2024-8088same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 15
Thu 1 Aug 2024· 2 record changes
2024-08-01CVE-2024-3219PSFstated at publication 3.13.0b4, now states 3.13.0rc1Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 3
2024-08-01CVE-2024-37956
vektor,inc.vk all in one expansion unit
Patchstack
stated at publication 9.98.1.0, now states 9.99.1.0Release branch starts at 0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 12
Thu 13 Jun 2024· 9 record changes
2024-06-13PSFstated at publication 3.8.18, now states 3.8.19Release branch starts at 0.not counted: Same claim, other operatorDays to revision 86
2024-06-13CVE-2023-6597same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 86
2024-06-13CVE-2024-0450same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 86
2024-06-13PSFstated at publication 3.10.13, now states 3.10.14Release branch starts at 3.10.0.not counted: Same claim, other operatorDays to revision 86
2024-06-13CVE-2023-6597same vendor as the line abovesame change as the line aboveRelease branch starts at 3.10.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 86
2024-06-13CVE-2024-0450same vendor as the line abovesame change as the line aboveRelease branch starts at 3.10.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 86
2024-06-13PSFstated at publication 3.11.8, now states 3.11.8Branches and original-value intervals are stated on each row.not counted: Same claim, other operatorDays to revision 15
2024-06-13CVE-2023-6597same vendor as the line abovesame change as the line aboveRelease branch starts at 3.11.0.Original value first replaced 2024-04-03; this value first seen 2024-06-13.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 15
2024-06-13CVE-2024-0450same vendor as the line abovesame change as the line aboveRelease branch starts at 3.11.0.Original value first replaced 2024-04-03; this value first seen 2024-06-13.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 15
2024-06-13PSFstated at publication 3.9.18, now states 3.9.19Release branch starts at 3.9.0.not counted: Same claim, other operatorDays to revision 86
2024-06-13CVE-2023-6597same vendor as the line abovesame change as the line aboveRelease branch starts at 3.9.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 86
2024-06-13CVE-2024-0450same vendor as the line abovesame change as the line aboveRelease branch starts at 3.9.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 86
2024-06-13CVE-2024-0450PSFstated at publication 3.12.2, now states 3.12.2Release branch starts at 3.12.0.Original value first replaced 2024-04-03; this value first seen 2024-06-13.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 15
Wed 5 Jun 2024· 1 record change
2024-06-05CVE-2023-51416
envialosimpleenvíalosimple
Patchstack
stated at publication 2.3, now states 2.3Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `unaffected_start` on the same or the next release — the same claim under the other operatorDays to revision 71
Thu 9 May 2024· 1 record change
2024-05-09CVE-2024-34383Patchstackstated at publication 7.6.1, now states 7.7.1Release branch starts at 0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 3
Thu 25 Apr 2024· 1 record change
2024-04-25CVE-2024-32677
loginpressloginpress pro
Patchstack
stated at publication 2.5.3, now states 3.0.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 1
Fri 1 Mar 2024· 12 record changes
2024-03-01CVE-2023-48674
dellcpg bios
stated at publication 1.9.0, now states 1.9.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
2024-03-01CVE-2023-48674
dellcpg bios
stated at publication 1.11.0, now states 1.11.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
2024-03-01CVE-2023-48674
dellcpg bios
stated at publication 1.12.0, now states 1.12.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
2024-03-01CVE-2023-48674
dellcpg bios
stated at publication 1.17.0, now states 1.17.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
2024-03-01CVE-2023-48674
dellcpg bios
stated at publication 1.20.0, now states 1.20.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
2024-03-01CVE-2023-48674
dellcpg bios
stated at publication 1.24.0, now states 1.24.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
2024-03-01CVE-2023-48674
dellcpg bios
stated at publication 1.26.0, now states 1.26.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
2024-03-01CVE-2023-48674
dellcpg bios
stated at publication 1.27.0, now states 1.27.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
2024-03-01CVE-2023-48674
dellcpg bios
stated at publication 1.27.1, now states 1.27.1Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
2024-03-01CVE-2023-48674
dellcpg bios
stated at publication 1.28.0, now states 1.28.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
2024-03-01CVE-2023-48674
dellcpg bios
stated at publication 1.32.0, now states 1.32.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
2024-03-01CVE-2023-48674
dellcpg bios
stated at publication 3.20.0, now states 3.20.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 0
Tue 13 Feb 2024· 1 record change
2024-02-13CVE-2023-0076
unknowndownload attachments
WPScan
stated at publication 1.2.24, now states 1.3Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 344
Mon 29 Jan 2024· 1 record change
2024-01-29CVE-2023-49657apachestated at publication 3.0.3, now states 3.0.3Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 6
Fri 15 Dec 2023· 1 record change
2023-12-15CVE-2023-3226
unknownpopup builder
WPScan
stated at publication 4.1.15, now states 4.2.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 81
Mon 23 Oct 2023· 1 record change
2023-10-23CVE-2023-2995
unknownleyka
WPScan
stated at publication 3.30.3, now states 3.30.4Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 34
Tue 26 Sep 2023· 1 record change
2023-09-26CVE-2023-1995
hitachihirdb server with addtional function
stated at publication 09-66-*, now states 09-66-/QRelease branch starts at 09-66.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 28
Wed 16 Aug 2023· 1 record change
2023-08-16CVE-2023-2330
unknowncaldera forms google sheets connector
WPScan
stated at publication 1.2, now states 1.3Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 30
Mon 14 Aug 2023· 1 record change
2023-08-14CVE-2023-1119
unknownsrbtranslatin
WPScan
stated at publication 2.4, now states 2.4.1Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 35
Tue 13 Jun 2023· 2 record changes
2023-06-13
unknowneasy forms for mailchimp
WPScan
stated at publication 6.8.8, now states 6.8.9Release branch starts at 0.not counted: Same claim, other operatorDays to revision 1 to 14
2023-06-13CVE-2023-1323same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 1
2023-06-13CVE-2023-2518same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 14
Tue 30 May 2023· 1 record change
2023-05-30CVE-2023-0779zephyrstated at publication v3.3, now states v3.3Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 1
Wed 10 May 2023· 6 record changes
2023-05-10CVE-2023-22813
sandiskibi mobile app
WDC PSIRT
stated at publication 4.21.0, now states 4.21.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 2
2023-05-10CVE-2023-22813
sandiskibi web app
WDC PSIRT
stated at publication 4.26.0-6126, now states 4.26.0-6126Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 2
2023-05-10CVE-2023-22813
western digital2 products
WDC PSIRT
stated at publication 4.21.0, now states 4.21.0Release branch starts at 0.not counted: Same claim, other operatorDays to revision 2
2023-05-10CVE-2023-22813same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 2
2023-05-10CVE-2023-22813same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 2
2023-05-10CVE-2023-22813
western digital2 products
WDC PSIRT
stated at publication 4.26.0-6126, now states 4.26.0-6126Release branch starts at 0.not counted: Same claim, other operatorDays to revision 2
2023-05-10CVE-2023-22813same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 2
2023-05-10CVE-2023-22813same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 2

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. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

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 →