Exploit-DB Exploits Scraper

Exploit-DB Exploits Scraper

Scrape Exploit-DB exploits by title, CVE, or category, up to a million per run. Every record includes the EDB-ID, CVE mappings, author, platform, type, and the full verified source code. Export to CSV, JSON, Excel, or XML.

Exploit-DB is the standard library of public exploit code, but manually searching and copying entries for threat intelligence or research is slow. This Actor reads the public exploit listings directly, filtering by free-text search or exploit type, and returns each match in a clean, flat schema. No API key or registration is needed.

Who uses it	What they scrape Exploit-DB for
Penetration testers	Build a local, searchable archive of verified exploits for a specific platform or service.
Vulnerability researchers	Monitor new entries for a specific CVE or keyword to track public exploit availability.
SOC analysts	Check if a newly announced CVE has a working public exploit to prioritize patching.
Threat intelligence teams	Collect the latest shellcode and remote exploits to feed into internal threat feeds.

What it does

This Actor collects Exploit-DB entries by search term or category and returns each exploit as a flat row with its EDB-ID, CVE references, author, platform, type, and full source code.

• 🔍 Free-text search: Filter by exploit title, application name, or CVE identifier like CVE-2024-1234.
• 📂 Category filter: Narrow results to webapps, remote, local, DoS, or shellcode exploits.
• 📊 Full metadata: Every row includes EDB-ID, author, platform, type, and all linked CVEs.
• 📝 Source code included: The complete, verified exploit code is returned in the dataset.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

What you can do with Exploit-DB data

📈 Monitor for new public exploits.

A SOC analyst runs the Actor daily with a search for a critical application, checking if any new entries appear so the team can assess the risk before an attack surfaces.

🗂️ Build an offline exploit archive.

A penetration tester scrapes all remote and webapps exploits for a target platform, creating a local, searchable dataset for use during engagements without internet access.

🔗 Map CVEs to working exploit code.

A vulnerability researcher searches for a specific CVE to confirm whether a working proof-of-concept exists on Exploit-DB, speeding up the triage process.

📊 Feed threat intelligence pipelines.

A threat intel team collects the latest shellcode and DoS exploits and pushes the structured data into their internal SIEM or threat feed for automated alerting.

Why choose this scraper

	What you get
Full source code	The complete exploit or shellcode is included in the output, not a link.
CVE mapping	Every linked CVE is parsed and returned in a dedicated field.
No API key	Reads the public Exploit-DB listings directly with no registration or authentication.
Flexible export	Save results as CSV, JSON, Excel, or XML for integration with your tools.

How it compares

This Actor focuses exclusively on scraping Exploit-DB exploit entries with full source code, while the alternatives below either map CVEs across multiple sources or include additional Exploit-DB sections like papers and dorks.

Feature	ParseForge	CVE-to-PoC Mapper	ExploitDB Scraper
Full exploit source code in output	Yes	Not listed	Yes
Filter by exploit type (webapps, remote, local, DoS, shellcode)	Yes	Not listed	Yes
Search by CVE identifier	Yes	Yes	Not listed
Scrapes GitHub and NVD in addition to Exploit-DB	Not listed	Yes	Not listed
Scrapes Google Hacking Database dorks	Not listed	Not listed	Yes
No API key or authentication required	Yes	Not listed	Not listed

Configure the run

Drive the Actor with a free-text search term or a CVE, and optionally narrow by exploit type. Filters run as each entry is read so only matches reach your dataset. The Input tab lists every parameter.

A first run with the defaults:

{
 "maxItems": 10
}

A larger pull:

{
 "maxItems": 200
}

Pricing

Pay-per-result: $0.021 per result collected. You pay only for the results written to your dataset.

Results collected	Approximate cost
100 results	$2.10
1,000 results	$21.00
10,000 results	$210.00

New Apify accounts start with $5 in free credit.

Free users

Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.

Run it

1. Create a free Apify account with $5 in credit.
2. Open the Exploit-DB Exploits Scraper.
3. Set your inputs and any filters, then click Start.
4. Export the results as CSV, Excel, JSON, or XML from the Dataset tab.

Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.

Use with AI agents (MCP)

Give an AI agent live access to Exploit-DB through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

$claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/exploit-db-exploits-scraper"

Then prompt it in plain language to run the scraper and read back the results.

Troubleshooting

Why am I getting no results?

Check your search term for typos. Try a broader term or clear the search field and use only a category filter. Also confirm that the 'Maximum exploits' field is set to a number greater than zero.

The run is taking too long.

Lower the 'Maximum exploits' count or narrow your search. A very broad search with a high limit will naturally take longer to collect.

Some fields are empty in my output.

Not every Exploit-DB entry has a CVE mapping, an author listed, or a platform specified. Empty fields reflect missing data on the source page itself.

The search by CVE is not finding an exploit I know exists.

Try searching by the application name or vulnerability title instead. The CVE field on Exploit-DB is not always populated, even when an exploit for that vulnerability exists.

I get an error when trying to export a very large dataset.

Try exporting in smaller batches or choose a streaming-friendly format like CSV. For datasets with millions of rows, consider splitting your run into multiple smaller searches.

FAQ

Question	Answer
Does this scraper return the full exploit source code?	Yes. The complete, verified source code for each exploit is included in the output dataset, not a link to the Exploit-DB page.
Can I search by CVE number?	Yes. Enter a CVE identifier like CVE-2024-1234 in the search field, and the Actor will return all Exploit-DB entries that reference that CVE.
What categories of exploits can I filter by?	You can filter by webapps, remote, local, DoS, or shellcode. Leave the filter on 'Any' to collect all types.
Do I need an API key or an OffSec account?	No. This Actor reads the public Exploit-DB listings directly. No registration, API key, or authentication is required.
How many exploits can I scrape in one run?	You set the maximum with the 'Maximum exploits' field, from 1 up to 1,000,000 per run. The Actor stops when it reaches that count or runs out of matching results.
What output formats are supported?	You can export your dataset to CSV, JSON, Excel, or XML directly from the Apify platform.
Does this scraper also collect Google Hacking Database entries?	No. This Actor focuses on the exploits, shellcodes, and papers sections of Exploit-DB. It does not scrape the GHDB dorks.
Is the exploit code safe to download and store?	The code is public proof-of-concept material from Exploit-DB. You should handle it with the same caution you would any security testing code, ideally in an isolated environment.
Can I schedule this Actor to run automatically?	Yes. You can set up a recurring schedule on Apify to run the Actor daily or weekly, checking for new exploits matching your search criteria.

Related actors

Browse the full ParseForge collection for more scrapers.

🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by OffSec Services Limited. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.