{"id":19007,"date":"2026-10-22T21:02:29","date_gmt":"2026-10-22T18:02:29","guid":{"rendered":"https:\/\/www.hyyat.com\/knowledgebase\/zero-day-vulnerability-cve\/"},"modified":"2026-10-22T21:02:32","modified_gmt":"2026-10-22T18:02:32","password":"","slug":"zero-day-vulnerability-cve","status":"publish","type":"docs","link":"https:\/\/www.hyyat.com\/en\/knowledgebase\/zero-day-vulnerability-cve\/","title":{"rendered":"Zero-Day Vulnerabilities and CVE Numbers: How to Read Security Alerts and Act Fast"},"content":{"rendered":"
\n
In short<\/b>Each security flaw gets a global ID such as CVE-2018-6389<\/span> and a severity score from 0 to 10 called CVSS. A \u201czero-day\u201d is a flaw attackers exploit before a fix exists. When you see an alert about something you use, ask three questions: is my version affected? Is there an update? And if not, what is the temporary measure?<\/div>\n
\"Zero-day<\/figure>\n

You get a message from your security tool, or read a headline: \u201cCritical flaw in plugin X, CVE-2025-XXXXX, score 9.8\u201d. The words may seem cryptic, but they carry everything you need to decide quickly.<\/p>\n

What is a CVE number?<\/h2>\n

CVE is a global identifier for each known flaw. It is the year followed by a sequence number, such as CVE-2018-6389<\/span>, the WordPress load-scripts flaw. Read the explanation of that flaw<\/a>. The number means every company and tool talks about the same flaw by the same name.<\/p>\n

The CVSS severity score<\/h2>\n
\n\n\n\n\n\n\n\n\n
Score<\/th>\nRating<\/th>\nSuggested action<\/th>\n<\/tr>\n<\/thead>\n
9.0 to 10<\/td>\nCritical<\/td>\nUpdate now, and apply a temporary measure if no update exists<\/td>\n<\/tr>\n
7.0 to 8.9<\/td>\nHigh<\/td>\nUpdate within a day or two<\/td>\n<\/tr>\n
4.0 to 6.9<\/td>\nMedium<\/td>\nUpdate in your weekly update cycle<\/td>\n<\/tr>\n
0.1 to 3.9<\/td>\nLow<\/td>\nUpdate with regular updates<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

The score alone is not enough. Also check whether exploiting the flaw needs a login. A flaw any visitor can exploit is more dangerous than one that needs an Administrator account.<\/p>\n

What is a zero-day?<\/h2>\n

It is a flaw that attackers discover and exploit before the developer knows about it or before a fix is released. The name comes from the developer having had \u201czero days\u201d to prepare. In that case there is no update to apply, so you need a temporary measure.<\/p>\n

What to do when a flaw is announced in something you use<\/h2>\n
    \n
  1. Check whether you are affected:<\/b> Compare your plugin or software version with the versions listed in the alert.<\/li>\n
  2. Update if a fix exists:<\/b> Back up, then update. Read updating WordPress safely<\/a>.<\/li>\n
  3. If there is no fix, disable or restrict:<\/b> Temporarily disable the plugin if you can, or block access to the affected page.<\/li>\n
  4. Rely on the web application firewall:<\/b> WAF rules are updated to block exploitation of new flaws before a fix arrives. Read what a WAF is<\/a>.<\/li>\n
  5. Scan your site:<\/b> If the flaw has been exploited for a while, make sure your site was not hit before you updated. Read the signs your website is hacked<\/a>.<\/li>\n<\/ol>\n

    Where to follow vulnerabilities<\/h2>\n