skills.rest
sjinks
sjinksCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

threat-model

Model WordPress vulnerability boundaries and generate structured triage reports.

Updated Mar 19, 2026
Search Tags:#security#vulnerability#threat-modeling#wordpress#boundary#multisite
One-click install
npx skills add https://github.com/sjinks/ai-wp-vulnerability-triage --skill threat-model-sjinks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: threat-model
Source: https://github.com/sjinks/ai-wp-vulnerability-triage/tree/main/.agents/skills/threat-model
Command: npx skills add https://github.com/sjinks/ai-wp-vulnerability-triage --skill threat-model-sjinks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

WordPress vulnerability triage often struggles to distinguish true security boundaries from expected plugin-related behavior. This Skill helps teams confirm boundary crossings across trust, site mode, and plugin purpose to improve accuracy in severity assessment.

Core Features & Use Cases

  • Boundary reasoning across WordPress trust boundaries (roles/capabilities), multisite vs single-site, and plugin-purpose boundaries to validate suspected vulnerabilities.
  • Guided triage workflow that prioritizes concrete attack paths and practical impact, then aligns with CVSS-like scoring and companion skills for verification.
  • Use Case: A reported vulnerability is evaluated by mapping entry points to required capabilities and site mode to determine if the issue crosses a boundary and warrants escalation.

Quick Start

Provide the vulnerable path, attacker role, site mode (single-site or multisite), and plugin purpose to assess boundary crossings and calibrate severity.

Frequently Asked Questions about threat-model

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

FAQPage Schema
How do I determine if a WordPress vulnerability crosses a security boundary?▼

To assess a WordPress vulnerability boundary crossing, you map the entry point to required attacker capabilities, site mode, and plugin purpose to differentiate true security violations from expected behavior.

How does multisite mode affect WordPress vulnerability triage compared to single-site?▼

Multisite mode affects vulnerability triage by introducing distinct trust boundaries and attacker roles across the network, requiring separate boundary analysis from single-site contexts to calibrate severity accurately.

What information do I need to model a WordPress vulnerability threat model?▼

To model a WordPress vulnerability threat, you need the vulnerable entry point, attacker capabilities, site mode, plugin purpose, and impact evidence to generate a structured triage report.

Why does my reported WordPress plugin vulnerability not warrant escalation?▼

A reported vulnerability may not warrant escalation if the suspected behavior aligns with expected plugin-purpose boundaries or the attacker already possesses the required capabilities for that action.

Can I use CVSS scoring alongside WordPress boundary threat modeling?▼

Yes, this threat modeling workflow prioritizes concrete attack paths and practical impact, then aligns with CVSS-like scoring to calibrate severity after confirming boundary crossings.

What is the best way to triage WordPress security vulnerabilities by trust boundaries?▼

The best way to triage WordPress security vulnerabilities is by reasoning across trust, site mode, and plugin-purpose boundaries to validate suspected issues and guide severity assessment.

Related Skills

Explore More Software Engineering Skills→
sjinkssjinks

vuln-triage-reachability

Trace WordPress plugin exploit paths from entry points to sinks.

Community
Advanced
codexstar69codexstar69
479

referee

Verify bug reports and assign CVSS scores with proof-of-concept examples.

Community
Advanced
adityaarsharmaadityaarsharma
2

orbit-life-activation

Audit WordPress plugin activation hooks for safety, idempotency, and performance.

Community
Intermediate
dreadnodedreadnode
11

vuln-critic

Filter low-quality and false positive vulnerability findings from scanners and agent output.

Official
Intermediate