exploit-poc-development
Turn a known/1-day vulnerability or a raw bug into a working, reliable PoC for an authorized target. Load when a CVE/advisory needs weaponizing, a public PoC needs adapting, or "write an exploit/PoC". Signals: a versioned service with a known CVE, a crash/primitive to develop, searchsploit hits.
v2026.10.14-ee0e0c52 installs+2 in 7 days27 StarsMITsynced 22 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/exploit-poc-developmentWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package968806c8…6ec5294f
968806c8659f…2c006ec5294f1 file · 1.3 KBScanMedium1 finding
- injection.no_confirmationSKILL.md:42
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/exploit-dev/exploit-poc-development@ee0e0c5
On this page
When it applies
You've identified a vulnerability (a versioned CVE, or your own discovered bug) and need a reliable proof-of-concept to demonstrate impact on an authorized target.
Why it works
A version+advisory tells you the root cause and the primitive; a methodical build turns that into repeatable code. For 1-days, most of the work is understanding and adapting, not inventing.
Method
- Identify precisely: exact product+version → advisory/CVE → root cause and affected code
path.
searchsploit <product version>; read the advisory and any public PoC. - Understand before running: never fire an unread exploit at a target — read the code, know what it does (esp. anything destructive), and check it matches your exact version.
- Set up a local mirror when possible (same version in a VM/container) to develop safely.
- Build incrementally: reach the vulnerable code → trigger the primitive (leak/overwrite/ inject) → stabilize → deliver payload. For web, a clean scripted request chain; for binaries, pwntools with the leak→control→shell steps.
- Make it reliable & minimal: parameterize target/port, add checks, remove noise; it must reproduce for a report/triager.
Gotchas
- Public PoCs are often broken, version-specific, or backdoored — read every line before running.
- Match the exact version/build; an off-by-one minor version silently fails or crashes the service.
- On live bug-bounty targets, prove the primitive without destructive payloads (no DoS/data loss).
Verify success
The PoC reproducibly demonstrates the vulnerability's impact (shell, read, auth bypass) against the authorized target/version, with clear steps.
References
Exploit-DB/searchsploit; pwntools docs; the vendor advisory/CVE for the specific bug.
Files in this version
- SKILL.md2.4 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumPrompt injection · injection.no_confirmationSKILL.md:42
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | 968806c8 | Signed | – |
More from NoorQureshi
All from this publisherMore in Reverse engineering and fuzzing
See the categoryAsk anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login