State.js v1.4.2+ has secure defaults for HTML includes:

✅ Safe by Default:

<!-- Template-based includes always work --><divdata-state-include="#my-template"></div>

⚠️ Requires Opt-In:

// External file fetches require explicit enablementstate.allowExternalIncludes=true;

Only enable external includes when:

• Fetching from HTTPS endpoints only
• Fetching from same-origin or trusted domains
• Your build/deployment pipeline is secure
• You have Content Security Policy headers configured

Add these headers to your server configuration:

Content-Security-Policy: default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'

For stricter security with DOMPurify:

Content-Security-Policy: default-src 'self'; script-src 'self' https://cdn.jsdelivr.net; style-src 'self' 'unsafe-inline'; require-trusted-types-for 'script'

For applications that must fetch external HTML, we strongly recommend using DOMPurify:

<scriptsrc="https://cdn.jsdelivr.net/npm/dompurify@3/dist/purify.min.js"></script><scriptsrc="state.js"></script><script>// DOMPurify will be auto-detected and usedstate.allowExternalIncludes=true;</script>

State.js will automatically use DOMPurify if it's available in the global scope.

Risk: External HTML includes could execute malicious JavaScript if the source is compromised.

Mitigation:

• External fetches disabled by default
• Template-based includes recommended
• DOMPurify auto-integration
• CSP headers recommended

Attack Examples:

<!-- ❌ UNSAFE: User-controlled URL --><divdata-state-include="${userInput}"></div><!-- ❌ UNSAFE: HTTP endpoint --><divdata-state-include="http://example.com/component.html"></div><!-- ✅ SAFE: Template reference --><divdata-state-include="#trusted-template"></div><!-- ⚠️ SAFER: HTTPS + same-origin + DOMPurify --><divdata-state-include="https://myapp.com/components/card.html"></div>

Risk: Previous versions used eval() which violated strict CSP policies.

Mitigation:

• v1.4.1+ uses custom expression parser instead of eval()
• All dynamic code execution is safe
• No CSP violations

• 🔒 External includes disabled by default
• ✅ Added opt-in flag for external fetches
• ✅ DOMPurify auto-integration
• ✅ Security warnings in console

• 🔒 Removed all eval() usage
• ✅ CSP-compliant expression parser
• ✅ Safe condition evaluation

• ⚠️ No security-specific changes

• ⚠️ External includes were enabled by default (XSS risk)
• ⚠️ Used eval() for expressions (CSP violations)
• 🚨 Upgrade recommended