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. |
|---|---|---|---|---|
| Wed 14 Jun 2023· 1 change | ||||
| 2023-06-14 | CVE-2023-28069 | whole record dell | stated at publication 7.1, now states 6.1CVSS v3.1 · base scoreHighMedium | Time to revision 70 days |
| Tue 13 Jun 2023· 1 change | ||||
| 2023-06-13 | CVE-2023-24880 | whole record microsoft | stated at publication 5.4, now states 4.4CVSS v3.1 · base scoreMediumMedium | Time to revision 91 days |
| Wed 7 Jun 2023· 1 change | ||||
| 2023-06-07 | CVE-2023-2909 | whole record ASUSTOR1 | stated at publication 6.0, now states 8.5CVSS v3.1 · base scoreMediumHigh | Time to revision 7 days |
| Thu 1 Jun 2023· 1 change | ||||
| 2023-06-01 | CVE-2023-33942 | whole record Liferay | stated at publication 6.4, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 8 days |
| Tue 9 May 2023· 2 changes | ||||
| 2023-05-09 | CVE-2023-24892 | whole record microsoft | stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHigh | Time to revision 56 days |
| 2023-05-09 | CVE-2023-28828 | whole record siemens | stated at publication 5.3, now states 5.9CVSS v3.1 · base scoreMediumMedium | Time to revision 28 days |
| Thu 4 May 2023· 1 change | ||||
| 2023-05-04 | CVE-2023-22921 | whole record Zyxel | stated at publication 7.2, now states 7.5CVSS v3.1 · base scoreHighHigh | Time to revision 3 days |
| Thu 27 Apr 2023· 3 changes | ||||
| 2023-04-27 | CVE-2023-21807 | whole record microsoft | stated at publication 5.8, now states 6.5CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2023-04-11; this value first seen 2023-04-27. | Time to revision 56 days |
| 2023-04-27 | CVE-2023-24858 | whole record microsoft | stated at publication 6.5, now states 7.5CVSS v3.1 · base scoreMediumHigh | Time to revision 44 days |
| 2023-04-27 | CVE-2023-24911 | whole record microsoft | stated at publication 6.5, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 44 days |
| Tue 18 Apr 2023· 1 change | ||||
| 2023-04-18 | CVE-2023-23379 | whole record microsoft | stated at publication 6.4, now states 7.8CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2023-04-14; this value first seen 2023-04-18. | Time to revision 59 days |
| Mon 17 Apr 2023· 1 change | ||||
| 2023-04-17 | CVE-2023-1728 | whole record TR-CERT | stated at publication 10.0, now states 9.8CVSS v3.1 · base scoreCriticalCritical | Time to revision 13 days |
| Fri 14 Apr 2023· 1 change | ||||
| 2023-04-14 | CVE-2023-28296 | whole record microsoft | stated at publication 8.4, now states 7.8CVSS v3.1 · base scoreHighHigh | Time to revision 3 days |
| Tue 11 Apr 2023· 4 changes | ||||
| 2023-04-11 | CVE-2023-21722 | whole record microsoft | stated at publication 4.4, now states 5.0CVSS v3.1 · base scoreMediumMedium | Time to revision 56 days |
| 2023-04-11 | CVE-2023-21778 | whole record microsoft | stated at publication 8.3, now states 8.0CVSS v3.1 · base scoreHighHigh | Time to revision 56 days |
| 2023-04-11 | whole record microsoft | stated at publication 8.4, now states 7.8CVSS v3.1 · base scoreHighHigh | Time to revision 56 days | |
| 2023-04-11 | CVE-2023-21815 | same vendor as the line above | same change as the line above | Time to revision 56 days |
| 2023-04-11 | CVE-2023-23381 | same vendor as the line above | same change as the line above | Time to revision 56 days |
| Thu 6 Apr 2023· 2 changes | ||||
| 2023-04-06 | CVE-2023-1725 | whole record TR-CERT | stated at publication 8.6, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 7 days |
| 2023-04-06 | CVE-2023-1014 | whole record TR-CERT | stated at publication 5.8, now states 7.5CVSS v3.1 · base scoreMediumHigh | Time to revision 7 days |
| Wed 5 Apr 2023· 2 changes | ||||
| 2023-04-05 | CVE-2023-0320 | whole record TR-CERT | stated at publication 6.5, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 16 days |
| 2023-04-05 | CVE-2023-1051 | whole record TR-CERT | stated at publication 6.5, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 13 days |
| Mon 3 Apr 2023· 2 changes | ||||
| 2023-04-03 | CVE-2023-28836 | whole record GitHub_M | stated at publication 4.4, now states 6.4CVSS v3.1 · base scoreMediumMedium | Time to revision 1 days |
| 2023-04-03 | CVE-2023-1766 | whole record TR-CERT | stated at publication 9.8, now states 6.1CVSS v3.1 · base scoreCriticalMedium | Time to revision 0 days |
| Fri 31 Mar 2023· 13 changes | ||||
| 2023-03-31 | CVE-2023-21610 | whole record adobe | stated at publication 4.3, now states 7.8CVSS v3.1 · base scoreMediumHigh | Time to revision 73 days |
| 2023-03-31 | CVE-2023-21614 | whole record adobe | stated at publication 7.8, now states 5.5CVSS v3.1 · base scoreHighMedium | Time to revision 73 days |
| 2023-03-31 | whole record adobe | stated at publication 3.5, now states 5.4CVSS v3.1 · base scoreLowMedium | Time to revision 10 days | |
| 2023-03-31 | CVE-2023-22256 | same vendor as the line above | same change as the line above | Time to revision 10 days |
| 2023-03-31 | CVE-2023-22257 | same vendor as the line above | same change as the line above | Time to revision 10 days |
| 2023-03-31 | CVE-2023-22258 | same vendor as the line above | same change as the line above | Time to revision 10 days |
| 2023-03-31 | CVE-2023-22259 | same vendor as the line above | same change as the line above | Time to revision 10 days |
| 2023-03-31 | CVE-2023-22260 | same vendor as the line above | same change as the line above | Time to revision 10 days |
| 2023-03-31 | CVE-2023-22261 | same vendor as the line above | same change as the line above | Time to revision 10 days |
| 2023-03-31 | CVE-2023-22262 | same vendor as the line above | same change as the line above | Time to revision 10 days |
| 2023-03-31 | CVE-2023-22263 | same vendor as the line above | same change as the line above | Time to revision 10 days |
| 3 more rows in this change are not listed here. Open all 11 rows → | ||||
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 →