Threat vs Attack vs Vulnerability vs Malware

By Bug Circuit Security Team
Threat vs Attack vs Vulnerability vs Malware

Is your own website affected? Check it free in 2 minutes.

Passive outside check only. Nothing is attacked, no signup.

A vulnerability is a weakness, a threat is something that could use it, an attack is someone actually trying, and malware is the harmful software an attacker may leave behind.

This glossary is for owners of small websites, WordPress and Shopify stores, indie SaaS and agency sites who see these words in scan reports, plugin warnings and client questionnaires and aren't sure which ones to worry about. You'll get one website example for each term, who is responsible (you, your host or the attacker), and a simple way to read advice correctly. You'll also get a short checklist you can finish this week.

The four terms at a glance

TermPlain meaningWebsite exampleWho is responsible
VulnerabilityA weakness that could be abusedAn outdated plugin with a known bugUsually you. Your host covers the server underneath.
ThreatAnyone or anything that could exploit a weaknessAutomated bots probing every WordPress site for that pluginThe attacker. You can only lower your exposure.
AttackAn actual attempt to exploit a weaknessA bot sends a crafted request to that plugin on your siteThe attacker. You and your host share defence.
MalwareMalicious software planted or used in an attackA hidden file that redirects visitors to a scam pageThe attacker plants it. You clean it up, with your host's help.

The short version: vulnerability is the unlocked window, threat is anyone who could climb through it, attack is the actual attempt to climb in, and malware is the thing they leave inside.

What is a vulnerability?

A vulnerability is a flaw or weakness in software, settings or processes that someone could abuse. NIST's glossary defines it as a weakness that a threat source could exploit. It is a condition, not an event. Nothing has happened yet.

Website example: your contact-form plugin has a known bug fixed in a newer version, and you haven't updated. Or your admin login has no second step and uses a password you also use elsewhere.

Who is responsible: mostly you. You choose and update your CMS (content management system, such as WordPress), themes and plugins, and you set the passwords. Your host handles the server, its operating system and the network around it. On managed hosting, the host may also update the core software. Check what yours actually covers.

Public vulnerabilities get an ID called a CVE (Common Vulnerabilities and Exposures), for example CVE-2021-44228. You can look them up in the National Vulnerability Database. A CVE tells you a weakness exists. It does not tell you anyone is using it against you.

What is a threat?

A threat is anyone or anything with the ability and the motive to cause harm. NIST defines it as a circumstance or event with the potential to harm a system. Threats exist whether or not you have a weakness.

Website example: automated bots that scan the internet all day, trying common login pages and known plugin bugs on every site they find. They don't care who you are. A small site is in their path just like a big one.

Who is responsible: the attacker is the source. You can't switch threats off. You can only make sure that when they show up, there is nothing easy to use.

This is why a threat alone is not scary. A threat plus a vulnerability is where risk begins.

What is an attack?

An attack is an actual attempt to exploit a weakness. It is an event, and it may succeed or fail.

Website example: someone sends a specially crafted input to a search box to try to trick your database, a technique called SQL injection. If your code handles input safely, the attack fails. If not, they might read data they shouldn't.

Who is responsible: the attacker carries it out. Defence is shared. You fix your code, plugins and passwords. Your host may block obvious abuse at the network level. Many failed attacks hit sites every day and cause no harm.

What is malware?

Malware is software built to do harm. NIST describes it as software or firmware intended to perform an unauthorized process that harms confidentiality, integrity or availability.

Website example: after getting in through that outdated plugin, an attacker uploads a hidden file called a web shell. It gives them a remote control panel for your site. Or they inject a script that sends your visitors to a fake pharmacy page.

Who is responsible: the attacker plants it. You and your host remove it, and you must also close the weakness it came through, or it returns.

Malware is an outcome or a tool. It is not the weakness itself.

How a vulnerability becomes an attack and where malware fits

Here is the usual chain on a small site, in order:

  1. A vulnerability exists. A plugin has a bug, and a fixed version is available.
  2. It becomes public. The bug gets a CVE and appears in databases like NVD. CISA also keeps a list of vulnerabilities known to be exploited in the real world.
  3. A threat notices. Bots start checking sites for that exact plugin version.
  4. An attack happens. A bot sends the exploit request to your site.
  5. It succeeds only if you are still exposed. If you have updated, the request should fail, because the bug it relies on is gone.
  6. Malware may follow. On a successful attack, the attacker uploads a web shell, a spam script or a card-skimming snippet.
  7. Damage shows up. Defaced pages, spam in search results, browser warnings, or stolen customer data.

You can break this chain at step 1 (patch), step 5 (block or harden) or step 7 (detect early and recover from backups). The earlier, the cheaper.

Vulnerability vs malware: the difference that trips people up

The confusion between a vulnerability and malware is the most common one in scan reports.

  • Vulnerability: a weakness. Your site is not necessarily harmed. Fix it with updates, config changes or code changes.
  • Malware: harmful code that is already there, or that is being delivered. This means something likely already went wrong. Fix it with cleanup, then fix the vulnerability behind it.

A useful test: Is something malicious present right now? If no, you have a vulnerability or a risk. If yes, you may have a compromise. In that case, go to our website hacked guide and act in that order: contain, clean, then close the hole.

How to read a scan report or security advice

When you see a finding, translate it:

  • 'Outdated software detected' or 'known CVE': vulnerability. Update it. This is not proof of an attack.
  • 'Missing security header': a small weakness that makes some attacks easier. You can check yours with the security headers tool.
  • 'Suspicious login attempts': attack attempts. Check whether any succeeded, and turn on a second login step.
  • 'Malware detected' or 'malicious file found': possible compromise. Treat it as urgent.
  • 'High severity': how bad it would be if abused. It is not a statement that it has been abused.

Severity and likelihood are different things. A high-severity bug on a page nobody can reach may matter less than a medium bug on your login page. A human reviewer helps with exactly this. The guide on manual vs automated testing explains why.

A short checklist you can finish this week

These steps lower your exposure to vulnerabilities, which is the part you control.

  1. Update everything. In WordPress, go to Dashboard, then Updates. With WP-CLI, wp plugin list --update=available shows what is out of date.
  2. Delete unused plugins and themes. Deactivated code can still be vulnerable.
  3. Turn on two-step login for admin accounts, and use a unique password for each.
  4. Check your headers. Run curl -I https://example.com (use your own domain) and look for lines like Strict-Transport-Security: max-age=31536000; includeSubDomains and X-Content-Type-Options: nosniff.
  5. Test your backups. Confirm you can restore one. A backup you've never restored is a guess.
  6. Run a free outside check with the free website security check to see what is publicly visible about your domain.

For a deeper view of what an attacker would notice about your site, see Is my website hackable?

For the common web weaknesses behind many real attacks, the OWASP Top 10 is the standard plain list to know.

Where a human audit fits

Automated tools are good at spotting known weaknesses. A person is better at finding how they connect on your site: a login flow, a checkout, a forgotten admin page. A Bug Circuit audit is a manual security test of one website by a real engineer, ending in a written report with each issue, severity, evidence, impact and fix steps. The Essential plan is $49 one-time and includes 3 audits within a month for one website. It is a small-site audit, not a compliance certificate or a multi-week enterprise test. Fixing is separate and quoted per issue, and there is no ongoing monitoring. See pricing for details.

Key takeaways

  • A vulnerability is a weakness, a threat is who could use it, an attack is the attempt, and malware is harmful software left behind.
  • You can't remove threats, but you can remove vulnerabilities. That is where your effort pays off.
  • A vulnerability finding is not proof you were attacked. A malware finding may mean you already were.
  • Patch first: updates, unused plugins removed, two-step login on, backups tested.
  • Read severity as 'how bad if abused', and ask separately how likely that is on your site.
Want certainty, not guesswork?

A real human security engineer audits your whole site by hand and sends a full report: every issue, its severity, and the exact fix. From $49, with a 14-day money-back guarantee.

Frequently asked questions

What is the difference between a threat, an attack and a vulnerability?
A vulnerability is a weakness, such as an outdated plugin. A threat is someone or something that could exploit it, such as bots scanning for that plugin. An attack is the actual attempt, which may succeed or fail.
What is the difference between vulnerability and malware?
A vulnerability is a weakness that could be abused, and nothing harmful may have happened yet. Malware is harmful software that is already planted or being delivered, often after an attack used a vulnerability. You fix vulnerabilities with updates and settings, and malware with cleanup plus closing the hole it came through.
Is a vulnerability the same as a hack?
No. A vulnerability is only a weakness. A hack, or successful attack, happens when someone uses that weakness. Many vulnerabilities are never exploited on a given site, especially if you patch quickly.
Can malware get onto my website without a vulnerability?
It usually needs a way in, such as an outdated plugin, a weak or stolen password, or a compromised account. Reused passwords and stolen logins count as weaknesses too. That's why updates, unique passwords and two-step login matter.
Who is responsible for website security, me or my host?
It's shared. Your host usually secures the server and network. You are usually responsible for your CMS, plugins, themes, code, passwords and user accounts. Check your host's documentation, because managed hosts cover more than basic ones.

Keep reading

See what attackers see, for free

Run the free passive check on your website. No login, no impact on your site, results in seconds.

Ready for the full manual audit? See pricing

Published by Bug Circuit. Written with AI assistance and reviewed for accuracy before publishing.