CVSS base score changed
| 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. |
|---|---|---|---|---|
| Fri 24 Jul 2026· 1 change | ||||
| 2026-07-24 | CVE-2026-15786 | whole record Wordfence | stated at publication 4.9, now states 4.4CVSS v3.1 · base scoreMediumMedium | Time to revision 2 days |
| Wed 8 Apr 2026· 82 changes | ||||
| 2026-04-082 commits | whole record Wordfence | stated at publication 7.6, now states 8.1CVSS v3.1 · base scoreHighHighBranches and original-value intervals are stated on each row. | Time to revision 1,167 days | |
| 2026-04-08 | CVE-2023-0550 | same vendor as the line above | same change as the line above | Time to revision 1,167 days |
| 2026-04-08 | CVE-2023-0554 | same vendor as the line above | same change as the line above | Time to revision 1,167 days |
| 2026-04-08 | CVE-2023-0555 | same vendor as the line above | same change as the line above | Time to revision 1,167 days |
| 2026-04-083 commits | whole record Wordfence | stated at publication 5.5, now states 4.4CVSS v3.1 · base scoreMediumMediumBranches and original-value intervals are stated on each row. | Time to revision 620 to 1,167 days | |
| 2026-04-08 | CVE-2023-0553 | same vendor as the line above | same change as the line above | Time to revision 1,167 days |
| 2026-04-08 | CVE-2024-6521 | same vendor as the line above | same change as the line above | Time to revision 620 days |
| 2026-04-08 | CVE-2024-6661 | same vendor as the line above | same change as the line above | Time to revision 621 days |
| 2026-04-08 | CVE-2023-2436 | same vendor as the line above | same change as the line above | Time to revision 1,044 days |
| 2026-04-08 | CVE-2024-6518 | same vendor as the line above | same change as the line above | Time to revision 620 days |
| 2026-04-08 | CVE-2024-6520 | same vendor as the line above | same change as the line above | Time to revision 620 days |
| 2026-04-08 | CVE-2023-1430 | whole record Wordfence | stated at publication 5.3, now states 6.5CVSS v3.1 · base scoreMediumMedium | Time to revision 1,035 days |
| 2026-04-08 | CVE-2023-3447 | whole record Wordfence | stated at publication 8.6, now states 7.6CVSS v3.1 · base scoreHighHigh | Time to revision 1,015 days |
| 2026-04-08 | CVE-2023-5250 | whole record Wordfence | stated at publication 6.4, now states 8.8CVSS v3.1 · base scoreMediumHigh | Time to revision 891 days |
| 2026-04-083 commits | whole record Wordfence | stated at publication 6.5, now states 6.4CVSS v3.1 · base scoreMediumMediumBranches and original-value intervals are stated on each row. | Time to revision 698 to 818 days | |
| 2026-04-08 | CVE-2024-0586 | same vendor as the line above | same change as the line above | Time to revision 793 days |
| 2026-04-08 | CVE-2024-2392 | same vendor as the line above | same change as the line above | Time to revision 748 days |
| 2026-04-08 | CVE-2024-2665 | same vendor as the line above | same change as the line above | Time to revision 729 days |
| 2026-04-08 | CVE-2024-2792 | same vendor as the line above | same change as the line above | Time to revision 729 days |
| 2026-04-08 | CVE-2023-6994 | same vendor as the line above | same change as the line above | Time to revision 818 days |
| 2026-04-08 | CVE-2024-2798 | same vendor as the line above | same change as the line above | Time to revision 716 days |
| 2026-04-08 | CVE-2024-4448 | same vendor as the line above | same change as the line above | Time to revision 698 days |
| 2026-04-08 | CVE-2024-0956 | whole record Wordfence | stated at publication 7.2, now states 4.9CVSS v3.1 · base scoreHighMedium | Time to revision 741 days |
| 2026-04-08 | CVE-2024-10078 | whole record Wordfence | stated at publication 7.3, now states 6.3CVSS v3.1 · base scoreHighMedium | Time to revision 537 days |
| 2026-04-083 commits | whole record Wordfence | stated at publication 6.5, now states 5.4CVSS v3.1 · base scoreMediumMediumBranches and original-value intervals are stated on each row. | Time to revision 117 to 761 days | |
| 2026-04-08 | CVE-2024-1125 | same vendor as the line above | same change as the line above | Time to revision 761 days |
| 2026-04-08 | CVE-2025-14446 | same vendor as the line above | same change as the line above | Time to revision 117 days |
| 2026-04-08 | CVE-2024-9860 | same vendor as the line above | same change as the line above | Time to revision 544 days |
| 2026-04-08 | CVE-2025-14064 | same vendor as the line above | same change as the line above | Time to revision 118 days |
| 2026-04-08 | CVE-2025-3953 | same vendor as the line above | same change as the line above | Time to revision 344 days |
| 2026-04-083 commits | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMediumBranches and original-value intervals are stated on each row. | Time to revision 19 to 965 days | |
| 2026-04-08 | CVE-2024-1126 | same vendor as the line above | same change as the line above | Time to revision 756 days |
| 2026-04-08 | CVE-2024-3893 | same vendor as the line above | same change as the line above | Time to revision 713 days |
| 2026-04-08 | CVE-2023-3244 | same vendor as the line above | same change as the line above | Time to revision 965 days |
| 2026-04-08 | CVE-2023-6969 | same vendor as the line above | same change as the line above | Time to revision 756 days |
| 2026-04-08 | CVE-2024-1689 | same vendor as the line above | same change as the line above | Time to revision 671 days |
| 2026-04-08 | CVE-2025-14441 | same vendor as the line above | same change as the line above | Time to revision 93 days |
| 2026-04-08 | CVE-2025-14581 | same vendor as the line above | same change as the line above | Time to revision 117 days |
| 2026-04-08 | CVE-2026-1253 | same vendor as the line above | same change as the line above | Time to revision 19 days |
| 16 more rows in this change are not listed here. Open all 24 rows → | ||||
| 2026-04-082 commits | whole record Wordfence | stated at publication 9.8, now states 6.5CVSS v3.1 · base scoreCriticalMediumBranches and original-value intervals are stated on each row. | Time to revision 588 to 658 days | |
| 2026-04-08 | CVE-2024-7857 | same vendor as the line above | same change as the line above | Time to revision 588 days |
| 2026-04-08 | CVE-2024-4742 | same vendor as the line above | same change as the line above | Time to revision 658 days |
| 2026-04-08 | CVE-2024-8353 | whole record Wordfence | stated at publication 10.0, now states 9.8CVSS v3.1 · base scoreCriticalCritical | Time to revision 558 days |
| 2026-04-08 | CVE-2025-1319 | whole record Wordfence | stated at publication 6.4, now states 7.2CVSS v3.1 · base scoreMediumHigh | Time to revision 404 days |
| 2026-04-082 commits | whole record Wordfence | stated at publication 5.3, now states 6.4CVSS v3.1 · base scoreMediumMediumBranches and original-value intervals are stated on each row. | Time to revision 215 to 699 days | |
| 2026-04-08 | CVE-2025-9849 | same vendor as the line above | same change as the line above | Time to revision 215 days |
| 2026-04-08 | CVE-2024-3916 | same vendor as the line above | same change as the line above | Time to revision 699 days |
| 2026-04-08 | CVE-2023-2079 | whole record Wordfence | stated at publication 8.3, now states 7.1CVSS v3.1 · base scoreHighHigh | Time to revision 1,003 days |
| 2026-04-082 commits | whole record Wordfence | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHighBranches and original-value intervals are stated on each row. | Time to revision 14 to 818 days | |
| 2026-04-08 | CVE-2023-6933 | same vendor as the line above | same change as the line above | Time to revision 793 days |
| 2026-04-08 | CVE-2023-6979 | same vendor as the line above | same change as the line above | Time to revision 818 days |
| 2026-04-08 | CVE-2024-4743 | same vendor as the line above | same change as the line above | Time to revision 672 days |
| 2026-04-08 | CVE-2025-5701 | same vendor as the line above | same change as the line above | Time to revision 307 days |
| 2026-04-08 | CVE-2026-1499 | same vendor as the line above | same change as the line above | Time to revision 61 days |
| 2026-04-08 | CVE-2026-4484 | same vendor as the line above | same change as the line above | Time to revision 14 days |
| 2026-04-08 | whole record Wordfence | stated at publication 8.8, now states 6.5CVSS v3.1 · base scoreHighMedium | Time to revision 165 to 740 days | |
| 2026-04-08 | CVE-2024-0608 | same vendor as the line above | same change as the line above | Time to revision 740 days |
| 2026-04-08 | CVE-2025-11893 | same vendor as the line above | same change as the line above | Time to revision 165 days |
| 2026-04-082 commits | whole record Wordfence | stated at publication 7.2, now states 6.4CVSS v3.1 · base scoreHighMediumBranches and original-value intervals are stated on each row. | Time to revision 279 to 739 days | |
| 2026-04-08 | CVE-2024-2948 | same vendor as the line above | same change as the line above | Time to revision 739 days |
| 2026-04-08 | CVE-2024-4262 | same vendor as the line above | same change as the line above | Time to revision 686 days |
| 2026-04-08 | CVE-2024-4709 | same vendor as the line above | same change as the line above | Time to revision 690 days |
| 2026-04-08 | CVE-2024-9017 | same vendor as the line above | same change as the line above | Time to revision 279 days |
| 2026-04-08 | CVE-2024-12599 | same vendor as the line above | same change as the line above | Time to revision 422 days |
| 2026-04-08 | CVE-2024-7856 | whole record Wordfence | stated at publication 9.1, now states 8.1CVSS v3.1 · base scoreCriticalHigh | Time to revision 588 days |
| 2026-04-08 | CVE-2025-12451 | whole record Wordfence | stated at publication 6.1, now states 4.4CVSS v3.1 · base scoreMediumMedium | Time to revision 49 days |
| 2026-04-08 | CVE-2025-14151 | whole record Wordfence | stated at publication 6.1, now states 7.2CVSS v3.1 · base scoreMediumHigh | Time to revision 110 days |
| 2026-04-08 | CVE-2025-14997 | whole record Wordfence | stated at publication 7.2, now states 8.8CVSS v3.1 · base scoreHighHigh | Time to revision 93 days |
| 2026-04-08 | CVE-2025-2636 | whole record Wordfence | stated at publication 9.8, now states 8.1CVSS v3.1 · base scoreCriticalHigh | Time to revision 363 days |
| 2026-04-08 | CVE-2026-0745 | whole record Wordfence | stated at publication 7.2, now states 5.5CVSS v3.1 · base scoreHighMedium | Time to revision 54 days |
| 2026-04-08 | CVE-2026-1937 | whole record Wordfence | stated at publication 9.8, now states 7.2CVSS v3.1 · base scoreCriticalHigh | Time to revision 50 days |
| 2026-04-08 | CVE-2026-2290 | whole record Wordfence | stated at publication 6.5, now states 3.8CVSS v3.1 · base scoreMediumLow | Time to revision 19 days |
| 2026-04-08 | CVE-2026-2991 | whole record Wordfence | stated at publication 9.8, now states 7.3CVSS v3.1 · base scoreCriticalHigh | Time to revision 21 days |
| 2026-04-08 | CVE-2023-6972 | whole record Wordfence | stated at publication 7.5, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 838 days |
| 2026-04-08 | CVE-2024-4838 | whole record Wordfence | stated at publication 8.8, now states 7.5CVSS v3.1 · base scoreHighHigh | Time to revision 692 days |
| 2026-04-08 | CVE-2025-10744 | whole record Wordfence | stated at publication 5.3, now states 5.9CVSS v3.1 · base scoreMediumMedium | Time to revision 190 days |
| Tue 3 Mar 2026· 1 change | ||||
| 2026-03-03 | CVE-2026-1927 | whole record Wordfence | stated at publication 4.3, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 26 days |
| Mon 15 Dec 2025· 1 change | ||||
| 2025-12-15 | CVE-2025-12377 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 32 days |
| Fri 19 Sep 2025· 1 change | ||||
| 2025-09-19 | CVE-2025-9851 | whole record Wordfence | stated at publication 5.4, now states 6.4CVSS v3.1 · base scoreMediumMedium | Time to revision 3 days |
| Wed 27 Aug 2025· 1 change | ||||
| 2025-08-27 | CVE-2025-5692 | whole record Wordfence | stated at publication 8.8, now states 6.3CVSS v3.1 · base scoreHighMedium | Time to revision 57 days |
| Mon 25 Aug 2025· 1 change | ||||
| 2025-08-25 | CVE-2025-8678 | whole record Wordfence | stated at publication 6.5, now states 5.9CVSS v3.1 · base scoreMediumMedium | Time to revision 3 days |
| Fri 13 Jun 2025· 1 change | ||||
| 2025-06-13 | CVE-2025-3623 | whole record Wordfence | stated at publication 8.1, now states 9.1CVSS v3.1 · base scoreHighCritical | Time to revision 31 days |
| Mon 9 Jun 2025· 1 change | ||||
| 2025-06-09 | CVE-2025-2780 | whole record Wordfence | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 67 days |
| Thu 13 Feb 2025· 1 change | ||||
| 2025-02-13 | CVE-2024-13440 | whole record Wordfence | stated at publication 7.5, now states 8.2CVSS v3.1 · base scoreHighHigh | Time to revision 5 days |
This kind is counted once per CVE record, so changes and records are the same number here. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.
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 →