A pegada
Older SPIP installations still appear on inherited marketing sites, community portals, and CMS estates. CVE-2016-7981 affects SPIP 3.1.2 and earlier when valider_xml reflects URL input into an HTML response without the expected encoding.
Como funciona
This active check confirms whether user-controlled input or workflow behavior crosses a security boundary. Public docs keep the explanation high-level so customers understand the risk. For check-specific questions about exact detection heuristics, active payload details, or source-code rule patterns, contact support@fixvibe.app.
O raio de impacto
If the affected endpoint is reachable, a crafted link may execute attacker-controlled script in a victim's browser under the SPIP site's origin. The practical impact depends on authentication state, cookie flags, administrative exposure, and what sensitive actions or data the SPIP origin can reach.
// what fixvibe checks
What FixVibe checks
FixVibe checks this class with verified-domain active testing that is bounded, non-destructive, and evidence-driven. Public reports describe the affected surface and remediation. For check-specific questions about exact detection heuristics, active payload details, or source-code rule patterns, contact support@fixvibe.app.
Defesas blindadas
Upgrade SPIP to 3.1.3 or newer. During rollout, restrict access to SPIP authoring/admin surfaces and ensure any remaining valider_xml output validates URL parameters and HTML-encodes reflected values before rendering.