XPath injection sink
What a xpath-injection finding of fallow security means, why it matters and how to fix it.
What it reports
Catalogue security candidate for CWE-643.
Security explains how fallow finds it.
Why it matters
The XPath engine parses the string as a query. An attacker who controls part of it can select other nodes, for example to skip a login check.
Example
xpath.select("//user[name='" + req.query.name + "']", doc);
Fix
Review the candidate trace before acting. Confirm attacker control, missing sanitization, and reachable runtime context, then fix with the category-appropriate safer API or add a reviewed suppression.
Facts
| Fact | Value |
|---|---|
| Issue type | xpath-injection |
| Rule id in SARIF output | security/xpath-injection |
| Command | fallow security |
| Default severity | off |
| Suppression comment | // fallow-ignore-next-line security-sink |
Fixable with fallow fix | No |
| Opt-in | Yes |
Note. Tainted-sink catalogue category; the security-sink suppression token covers every category.