injection-checking

Injection vulnerability triage involves confirming attacker-controlled input reaches a dangerous execution environment, then routing the issue to the correct deep-topic workflow based on the specific sink type identified.

The best way to distinguish between XSS, SQLi, and SSRF is flow-based triage: mapping where attacker-controlled input ends up, such as a browser context, database, or server-side request, to select the matching exploit workflow.

Yes, sink identification works for uncommon injection types like XPath or LDAP by referencing a companion guide that routes these injection-style variations to appropriate workflows when they appear in real stacks.

To route a suspicious login request to the correct exploit workflow, first identify the final sink of the attacker-controlled input, then select the matching deep-topic skill for that sink environment.

You should use a routing skill instead of a dedicated SQLi or command injection tool when you need to classify ambiguous injection-class vulnerabilities and confirm the input reaches a dangerous interpreter before committing to a specific deep-topic workflow.