Every change, newest first
Showing changes seen on 2026-04-01. Every day
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.
| 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 1 Apr 2026· 28 record changes | |||||
| 2026-04-01 | Affected range extended | CVE-2025-32192 | ultrapressultra addons lite for elementor Patchstack | stated at publication 1.1.8, now states 1.1.9Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 1.1.8 still holds | not dated |
| 2026-04-01 | Affected range extended | CVE-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 holds | not dated |
| 2026-04-01 | Affected range extended | CVE-2025-32195 | ecwid by lightspeed ecommerce shopping cartecwid shopping cart Patchstack | stated 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 holds | not dated |
| 2026-04-01 | Affected range extended | CVE-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 holds | not dated |
| 2026-04-01 | Affected range extended | CVE-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 holds | not dated |
| 2026-04-01 | Affected range extended | CVE-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 bump | Days to revision 355 |
| 2026-04-01 | Affected range extended | CVE-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 operator | Days to revision 296 |
| 2026-04-01 | Affected range extended | CVE-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 bump | Days to revision 357 |
| 2026-04-01 | Affected range extended | CVE-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 bump | Days to revision 204 |
| 2026-04-01 | Affected range extended | CVE-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 bump | Days to revision 122 |
| 2026-04-01 | Affected range extended | CVE-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 bump | not dated |
| 2026-04-01 | Affected range extended | CVE-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 bump | Days to revision 230 |
| 2026-04-01 | Affected range extended | CVE-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 bump | Days to revision 216 |
| 2026-04-01 | Affected range extended | CVE-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 operator | Days to revision 187 |
| 2026-04-01 | Affected range extended | CVE-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 operator | Days to revision 187 |
| 2026-04-01 | Affected range extended | CVE-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 operator | Days to revision 187 |
| 2026-04-01 | Affected range extended | CVE-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 operator | Days to revision 561 |
| 2026-04-01 | Affected range extended | CVE-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 bump | Days to revision 481 |
| 2026-04-01 | Affected range extended | CVE-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 bump | Days to revision 478 |
| 2026-04-01 | Affected range extended | CVE-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 bump | Days to revision 474 |
| 2026-04-01 | Affected range extended | CVE-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 bump | Days to revision 456 |
| 2026-04-01 | Affected range extended | CVE-2025-22636 | vicente ruiz gálvezvr-frases Patchstack | stated 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 bump | Days to revision 349 |
| 2026-04-01 | CVSS base score changed | CVE-2026-29014 | whole record VulnCheck | stated at publication 9.3, now states 9.8Assessments not comparable · base scoreCriticalCriticalNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 0 |
| 2026-04-01 | CVSS base score changed | CVE-2026-34430 | whole record VulnCheck | stated at publication 8.6, now states 8.8Assessments not comparable · base scoreHighHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 0 |
| 2026-04-01 | CVSS base score changed | whole record VulnCheck | stated at publication 8.5, now states 7.8Assessments not comparable · base scoreHighHighnot counted: CVSS version set changed | Days to revision 27 | |
| 2026-04-01 | same kind of change as the line above | CVE-2026-27748 | same vendor as the line above | same change as the line aboveNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 27 |
| 2026-04-01 | same kind of change as the line above | CVE-2026-27749 | same vendor as the line above | same change as the line aboveNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 27 |
| 2026-04-01 | same kind of change as the line above | CVE-2026-27750 | same vendor as the line above | same change as the line aboveNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 27 |
| 2026-04-01 | CVSS base score changed | CVE-2026-35056 | whole record VulnCheck | stated at publication 8.8, now states 8.6Assessments not comparable · base scoreHighHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 1 |
Rows, not records: a moved fix version or an extended range counts once per record, product and release branch; an added product once per record and product; every other kind once per record or advisory. 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 →