vuln-triage-reachability

Trace WordPress plugin exploit paths from entry points to sinks.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/sjinks/ai-wp-vulnerability-triage --skill vuln-triage-reachability
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vuln-triage-reachability
Source: https://github.com/sjinks/ai-wp-vulnerability-triage/tree/main/.agents/skills/vuln-triage-reachability
Command: npx skills add https://github.com/sjinks/ai-wp-vulnerability-triage --skill vuln-triage-reachability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Confirm whether the claimed vulnerable path is real, reachable, and correctly scoped in the context of a WordPress vulnerability advisory.

Core Features & Use Cases

  • Validate entry points, sources, and sinks to verify exploitability within a triage workflow.
  • Check guard rails and boundary semantics (nonce, capability checks, sanitization) to ensure accurate scope.
  • Integrate with companion skills for threat modeling, CVSS calculation, and runtime evidence gathering.

Quick Start

Identify an entry point and feed the vulnerable source and claimed advisory scope into the skill to verify reachability and correctness.

Frequently Asked Questions about vuln-triage-reachability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify if a WordPress plugin vulnerability advisory is actually reachable?

To verify vulnerability reachability, identify the plugin's entry point, trace controllable input sources to the sink, and check for boundary semantics like nonce or capability checks to confirm the exploit path is real and correctly scoped.

What is vulnerability triage reachability analysis in a security advisory context?

Vulnerability triage reachability analysis is the process of validating whether a claimed vulnerable path is real and accessible. It requires identifying the entry point, input source, sink, guard checks, and execution scope to confirm exploitability.

How do I check guard rails and boundary semantics during WordPress vulnerability triage?

Check guard rails and boundary semantics by tracing input sources to sinks and verifying if nonce validations, capability checks, or sanitization routines block the exploit path across frontend and admin contexts, ensuring accurate vulnerability scope.

What inputs are required to trace an exploit path for threat modeling and CVSS workflows?

Tracing an exploit path requires five inputs: the entry point, the controllable input source, the vulnerable sink, existing guard checks, and the execution scope. These elements validate reachability and integrate with CVSS calculations.

Does vulnerability reachability analysis work for both frontend and admin WordPress contexts?

Yes, vulnerability reachability analysis applies across both frontend and admin WordPress contexts. It evaluates guard checks and boundary semantics within each specific scope to determine if the claimed exploit path is genuinely accessible.