Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
A CVE is a worldwide number for a vulnerability. IPA explains it as a common identifier that uniquely identifies a vulnerability contained in an individual product. It is written like "CVE-2026-103671": the letters CVE, then a year, then a serial number.
How does a CVE work?
Think of a parcel tracking number. If each carrier called the same parcel by a different name, you could not tell where it was. In the same way, if product makers and research bodies each published information on a vulnerability under their own names, you could not tell whether they were talking about the same hole.
CVE prevents that confusion. The same hole gets the same number, so you can judge whether countermeasure information from different organizations points to the same vulnerability. IPA also explains that it can be used for cross-reference and linking. The year in the number is not the year of discovery. It is the year the number was assigned or the year of publication.
You will meet CVE numbers in vendor advisories, in JVN entries, and in notices from security agencies. Because every one of these sources can use the same number, you can follow one hole across all of them without guessing. Reading one is simple. A vulnerability in a plugin for EC-CUBE, published on 14 October 2026, is known by the JVN advisory number and also as CVE-2026-103671. JVN records that the developer has already confirmed attacks that use this vulnerability.
Why do CVEs matter?
For a site operator, the number is the way in to the question "does this concern me?" An advisory lists the CVE number together with the affected product name and version. Compare the names and versions of the plugins you use, and you can judge whether an update is needed.
The number does not express how serious the hole is. Severity is shown by a different mechanism, the score called CVSS. Remember it this way: the number tells you which hole, and the score tells you how dangerous.
Also, a number does not mean a fixed version has been released. For a zero-day, where no fixed version exists, you cannot update even though a number exists, and you wait for the workaround its maker gives. Some holes have no number, so do not stop updating.
What should you check when you see a CVE number?
- Note the product name and the affected versions listed with the number.
- Compare them with the plugin and theme names and versions in your admin screen.
- If your version is affected, update to the fixed version. If none exists yet, follow the workaround its maker gives.
- Read the severity score as well, and read the advisory to see whether attacks have been confirmed.
Whether a number applies to your plugins is something we can look at together: contact us.
One more practical tip: copy the CVE number into your update record. When someone later asks why a plugin was updated on a given day, the number lets anyone find the same advisory again. It also makes talks with an agency clearer, because naming the number is easier than describing the hole in your own words.
Related terms
- Vulnerability: the security hole itself
- CVSS: the score that shows severity from 0 to 10
Frequently asked questions
Who assigns CVE numbers?
The CVE Program explains that numbers are assigned by CNAs (CVE Numbering Authorities) around the world. IPA explains that MITRE, a US nonprofit, assigns them. A site operator never assigns one, and stays on the side that reads the numbers in advisories.
Is a vulnerability without a CVE number safe?
No. Some holes exist before a number is assigned, and some configuration flaws do not qualify for a number. Having a number is not a guide to danger, so check it together with the official advisories of the products you use.
How do I find out from a CVE number whether my site is affected?
Search the number on a vulnerability information site such as JVN, which lists the affected products and versions. Compare the names and versions of your plugins and themes, and if one matches, update to the fixed version its maker releases.
Next step
The free URL check shows only what is visible from outside. To go through an advisory with us, contact us. For the wider picture of holes, start with vulnerability.
Frequently asked questions
Who assigns CVE numbers?
The CVE Program explains that numbers are assigned by CNAs (CVE Numbering Authorities) around the world. IPA explains that MITRE, a US nonprofit, assigns them. A site operator never assigns one, and stays on the side that reads the numbers in advisories.
Is a vulnerability without a CVE number safe?
No. Some holes exist before a number is assigned, and some configuration flaws do not qualify for a number. Having a number is not a guide to danger, so check it together with the official advisories of the products you use.
How do I find out from a CVE number whether my site is affected?
Search the number on a vulnerability information site such as JVN, which lists the affected products and versions. Compare the names and versions of your plugins and themes, and if one matches, update to the fixed version its maker releases.