# View exploits

An exploit is a demonstration of how a vulnerability can be taken advantage of. When an exploit is widely published, it is commonly referred to as an exploit "in the wild."

## View exploits in Projects

In the Snyk web UI, navigate to the Project detail page for any of your Projects. Exploit information is shown for each issue found in that Project:

<figure><img src="https://2533899886-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MdwVZ6HOZriajCf5nXH%2Fuploads%2FDYR3t0Pf64pgG1fbwUm0%2FExploit-in-issue.png?alt=media&#x26;token=b752856b-e8d6-4a9d-a6fc-488d10747b3f" alt="View exploit information in Projects"><figcaption><p>Exploit information in Projects</p></figcaption></figure>

You can filter detected issues in your Projects by exploit maturity, to see whether a specific vulnerability has an exploit in the wild, and if so, how mature that exploit is. This helps you prioritize and attend to the most important and risky vulnerabilities first.

The filter has the following options:

<figure><img src="https://2533899886-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MdwVZ6HOZriajCf5nXH%2Fuploads%2Fgit-blob-5b87890176e4968b58196f3a1b090d7fd60730e3%2Fimage%20(53).png?alt=media&#x26;token=ba60e570-cacd-497e-bdcb-34e7f6b91044" alt="Options in the exploit maturity filter"><figcaption><p>Options in the exploit maturity filter</p></figcaption></figure>

* **Mature:** Snyk has a published code exploit for this vulnerability.
* **Proof of concept:** Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.\
  Proof of concept vulnerability patches cannot be disabled and will appear in fix PRs where they are found
* **No known exploit:** Snyk did not find a proof-of-concept or a published exploit for this vulnerability.
* **No data**: The issue is not a vulnerability, but a license issue or a vulnerability advisory.

## View exploits availability in Reports

You can check the availability of exploit information in the Reports section.

<figure><img src="https://2533899886-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MdwVZ6HOZriajCf5nXH%2Fuploads%2Fri1rcgGthSq2bB1TH2UT%2FExploit-in-reports.png?alt=media&#x26;token=338ec5b7-4f0d-4e09-8ff2-7969112c6d54" alt="View exploits in Reports"><figcaption><p>View exploits in Reports</p></figcaption></figure>

## How exploits are determined

Information about the existence and status of an exploit is collected from various sources.

The security analysts at Snyk curate information on new exploits and an automated process explores structured and unstructured data from multiple exploit sources.

Examples of structured data are the [Known Exploited Vulnerabilities Catalog](https://www.cisa.gov/known-exploited-vulnerabilities-catalog) by CISA (Cybersecurity and Infrastructure Security Agency) [Exploit DB](https://www.exploit-db.com/). Examples of unstructured data include blogs, forums, and social media sites like X (formerly known as Twitter).
