react-doctor/active-static-asset

A browser-reachable SVG that contains a `<script>` tag or `on*` event handler runs that code in your origin when someone opens it, which can lead to cross-site scripting.

Validation prompt

Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.

Two detection branches. (1) For a .svg file that is browser-reachable (under public/, dist/assets/, .next/static/, out/, a generated bundle, or a .map), it fires when the SVG body contains a <script tag or an inline on{load,error,click,mouseover}= event handler: an executable SVG that runs script when opened same-origin (escalated to an error-level finding). (2) For production source (.js/.ts/.tsx) or config/CI files, it fires on the literal dangerouslyAllowSVG: true or an <object|embed|iframe> whose data/src points at a .svg file.

Suppress when: a first-party, fully-trusted SVG you author whose script/handlers are intentional and never mixed with user-uploaded SVGs, or a dangerouslyAllowSVG: true config where every served SVG is sanitized/first-party and the response already sets an attachment disposition and a script-blocking CSP.

Evidence boundary

The diagnostic proves only that the detector’s modeled source pattern matched. It does not prove runtime impact, product intent, rendered failure, or that one remediation is correct.

Establish the environment, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.

Record one outcome:

• Confirmed failure: The required evidence establishes the violation.
• Rejected: A documented exception or false-positive predicate applies.
• Needs evidence: Named evidence can still be collected.
• Unavailable: Required evidence cannot be collected in this run.
• Waived with evidence: An authorized, scoped exception applies to an established failure.
• Observation: The review records an optional tradeoff without claiming a defect.

A waiver records its scope, authority, evidence, and review condition. It is not a pass or false positive.

Default severity is registry metadata. Use the occurrence’s JSON severity after repository configuration when ordering real findings.

Fix prompt

Apply this candidate correction only after the required evidence confirms the risk.

Serve SVGs as inert images: reference them with <img src=...> instead of <object>, <embed>, or <iframe>, so embedded scripts and handlers never run. If you must serve raw SVG, sanitize it first (for example DOMPurify with the SVG profile) to strip <script> and on* handlers, deliver it from a cookieless origin with Content-Disposition: attachment, and set a Content-Security-Policy that blocks script-src and object-src. Avoid dangerouslyAllowSVG: true in Next image config unless every SVG is first-party and sanitized.

Repository-wide copy prompt

Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.