Glossary

Exploit

Definition

An exploit is code or a method that takes advantage of a security weakness to produce an unintended result.

An exploit turns a weakness into a specific effect. Its success depends on the affected version, configuration and access available.

A customer may include “Exploit” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.

An exploit is a method or piece of code that takes advantage of a security weakness. It causes behaviour the system was not meant to allow, such as revealing information, running commands or bypassing a restriction. The weakness is the vulnerability; the exploit is a way to use it.

An exploit may be used by an attacker or by an authorised tester demonstrating a problem. Its existence does not establish that your business has been attacked. Equally, a known exploit can make a reachable weakness more urgent to address.

Hypothetical example: a hosting supplier tells a small charity that its website plug-in has a flaw and a publicly available exploit. The charity needs to establish whether its installed version is affected and exposed, then apply the relevant fix. It should not assume that every website using the plug-in has already been compromised.

Check whether the affected product version and configuration match the vulnerability, apply the vendor's mitigation or fix, then verify the result. Exploit availability and observed attacks are separate facts; neither alone proves that a specific environment was compromised. A demonstration on one system may depend on permissions or settings absent elsewhere. Avoid trying unfamiliar exploit code on a live service: authorised validation needs a defined scope and a plan for possible disruption.

Sources: MITRE development of exploits; OWASP injection explanation.