Exploit Execution & Payload Control

Use When

• A validated primitive exists and the next phase is controlled exploit implementation, payload hardening, chaining, reliability testing, or impact proof.
• The task is explicitly a lab exploit-development exercise with clear boundaries.

Handoff Criteria

• Hand off to CVE, input/protocol, authz, XSS, OOB, or business-logic workflows when the primitive is not yet validated.
• Hand off to reporting when impact proof and reproducibility are complete.

Output Schema

• Exploit plan: preconditions, primitive, payload strategy, safety guardrails
• Execution log: step, result, evidence
• Final capability statement: what attacker can do after exploitation