sast-xxe

Identify and document XML parsing points vulnerable to XXE across a codebase.

1.3k|61|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/utkusen/sast-skills --skill sast-xxe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sast-xxe
Source: https://github.com/utkusen/sast-skills/tree/main/sast-files/.agents/skills/sast-xxe
Command: npx skills add https://github.com/utkusen/sast-skills --skill sast-xxe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps security teams quickly locate and assess XXE vulnerabilities by systematically analyzing a codebase for XML parsing points that lack explicit hardening against external entities.

Core Features & Use Cases

  • Three-phase XXE workflow: reconnaissance to identify parsing sites, batched verification to trace user input, and merge to consolidate results.
  • Artifact generation: outputs are written to sast/xxe-recon.md, sast/xxe-batch-*.md, and the final sast/xxe-results.md for reporting.
  • Prerequisites awareness: depends on sast/architecture.md to provide context about the tech stack and entry points.

Quick Start

Run the XXE detection workflow against a codebase to locate unsafe XML parsing points and verify exploitable paths.

Frequently Asked Questions about sast-xxe

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

FAQPage Schema
How do I scan a codebase for XXE vulnerabilities?

To scan for XXE vulnerabilities, this Skill runs a three-phase workflow: reconnaissance to identify XML parsing points, batched verification to trace user input, and a merge phase to consolidate results into sast/xxe-results.md.

What is the best way to detect unsafe XML parsing points during static analysis?

The best way to detect unsafe XML parsing points is using a phased static-analysis workflow that systematically locates parsers lacking explicit hardening against external entities and traces exploitable paths.

How does the XXE detection workflow verify if a parsing point is exploitable?

The XXE detection workflow verifies exploitable parsing points during the batched verify phase, which traces user input to the identified XML parsing locations and documents the findings in sast/xxe-batch-*.md files.

Do I need an architecture document to perform XXE code review?

Yes, you need an architecture document to perform XXE code review. This workflow depends on sast/architecture.md to provide necessary context about the tech stack and entry points before identifying XML parsing sites.

What artifacts and reports are generated when checking a project for XXE vulnerabilities?

Checking a project for XXE vulnerabilities generates markdown artifacts including sast/xxe-recon.md for reconnaissance, sast/xxe-batch-*.md for verification batches, and the final consolidated sast/xxe-results.md report.

Why does static analysis for XXE require a phased workflow instead of a single scan?

Static analysis for XXE requires a phased workflow because locating XML parsing points, verifying user input traces, and consolidating findings across a project architecture demands separate stages to accurately validate exploitable paths.