Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
A vulnerability is a security hole. It is a flaw in how a program is built or set up that lets an attacker get in. Japan's Ministry of Internal Affairs and Communications (MIC), in its cybersecurity site for the public, describes it as a defect caused by a program fault or a design mistake, also called a security hole.
How does a vulnerability work?
Think of a house. The front door may be locked, but if a window latch is broken, someone can still get in. A vulnerability is that broken latch. The trouble is that the owner may not notice that the site can be entered from outside.
Holes appear for two main reasons. One is a mistake in how the program was written. The other is a faulty setting or a problem in operation. IPA counts as website vulnerabilities even the state where personal information is not managed under proper access control.
When a hole is found, it gets a worldwide number (CVE) and a severity score (CVSS), and its maker releases a fixed version. A hole that is attacked before a fixed version exists is called a zero-day. How to check for holes is covered in hacking countermeasures, and for help you can contact us.
Why do vulnerabilities matter?
Leaving a vulnerability open raises the risk of unauthorized access and virus infection. MIC asks users to update as quickly as possible. In IPA's Top 10 Information Security Threats 2026, attacks that exploit system vulnerabilities rank fourth among threats to organizations.
On small company sites, the usual cause is not an exotic attack but a hole in a part nobody remembered to update. WordPress plugins and programs written by other people (dependencies) run as part of the site even if you never wrote them.
What you can do today is plain work. Check the version of each part, update any that are not current, and delete the ones you do not use. If you worry that an update will change how the site behaves, take a backup first.
What should a site operator do about vulnerabilities?
- Open the admin screen and note the version of WordPress core, each theme, and each plugin.
- Update anything that is not the latest, after taking a backup.
- Delete plugins and themes you do not use, since an installed part can still hold a hole.
- Ask your agency who watches for new vulnerabilities and who applies updates.
- For screens behind login and for features built specially for you, arrange an assessment by an expert.
None of this needs special tools. It needs a habit: a regular day for checking versions, and one named person who owns the job.
A useful habit is to treat every installed part as your responsibility, even if an agency installed it. When a notice about a part you use appears, you can then answer three questions quickly: is my version affected, is a fixed version out, and who will apply it?
Related terms
- CVE: the worldwide number attached to a vulnerability
- CVSS: the score that shows a vulnerability's severity
- Zero-day: a vulnerability with no fixed version yet
- Dependencies: parts, written by others, that your program uses
Frequently asked questions
Is a vulnerability the same as a bug?
No. A bug is any program defect, including ones unrelated to security, such as a broken page layout. A vulnerability is a defect that an attack can abuse to cause harm.
How can I find out whether my site has a vulnerability?
First check in the admin screen that WordPress core, themes, and plugins are on the latest versions. The free URL check looks only at the outside of your site. Screens behind login and custom-built features need an assessment by an expert.
Does updating remove a vulnerability?
A known vulnerability is closed by updating to the fixed version its maker releases. Old parts that cannot be updated, and holes caused by faulty settings, remain. Along with updating, delete parts you do not use and review your settings.
Next step
The free URL check looks at your site from the outside only. For the overall picture of countermeasures, see hacking countermeasures, and for the scope of an assessment, see the web application assessment. If you are unsure, contact us.
Frequently asked questions
Is a vulnerability the same as a bug?
No. A bug is any program defect, including ones unrelated to security, such as a broken page layout. A vulnerability is a defect that an attack can abuse to cause harm.
How can I find out whether my site has a vulnerability?
First check in the admin screen that WordPress core, themes, and plugins are on the latest versions. The free URL check looks only at the outside of your site. Screens behind login and custom-built features need an assessment by an expert.
Does updating remove a vulnerability?
A known vulnerability is closed by updating to the fixed version its maker releases. Old parts that cannot be updated, and holes caused by faulty settings, remain. Along with updating, delete parts you do not use and review your settings.