react-doctor/svg-filter-clickjacking-risk

Applying CSS or SVG filters over a cross-origin iframe can be used for clickjacking or to read pixels from framed content the attacker should not see.

Validation prompt

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

Fires in production source when an <iframe> sits within ~700 characters of a CSS filter reference (filter: url(#…), in either order) or an SVG filter primitive (<feDisplacementMap>, <feColorMatrix>, <feComposite>, <feTile>, <feMorphology>) near an iframe: the textual proximity used to build an SVG/CSS-filter clickjacking or visual-exfiltration primitive over an embedded frame. Detection is case-insensitive substring proximity, not real DOM scoping.

Suppress when: the iframe and the filter are unrelated code that merely happen to fall within the window (a filter applied to a chart/image elsewhere in the same file), or the iframe is same-origin first-party UI where filtering is intentional decoration: confirm the filter actually applies to a cross-origin or privileged frame.

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.

Do not apply CSS or SVG filters to cross-origin or privileged iframes; remove the filter/fe* primitive from the embedded frame's render path. Protect sensitive pages from being framed with Content-Security-Policy: frame-ancestors 'self' (or 'none') plus X-Frame-Options. Apply visual effects only to first-party content you control, never to embedded third-party UI.

Repository-wide copy prompt

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