# CVE-2026-104676: Zion Builder <= 3.6.17 - Author+ Stored XSS via SVG Upload

Status: published. Published: 2026-11-10. Updated: 2026-11-10.

The Zion Builder  WordPress plugin through 3.6.17 does not sanitize uploaded SVG files or validate their contents before storing them in a publicly accessible location and serving them from the site's own origin, allowing authenticated users with the Author role or above to upload a crafted SVG containing JavaScript that executes in the browser of anyone who opens the file.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Unknown / Zion Builder: ≥ 0; ≤ 3.6.17 (affected, semver). Source: CNA: WPScan

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-79

## Exploit evidence

- exploit: https://wpscan.com/vulnerability/c7f45006-a654-4d3f-83b0-727e468f487e/ (CNA: WPScan)

## References

- https://wpscan.com/vulnerability/c7f45006-a654-4d3f-83b0-727e468f487e/ (CNA: WPScan; exploit, vdb-entry, technical-description)

## Provenance

- CNA: WPScan: https://www.cve.org/CVERecord?id=CVE-2026-104676; retrieved 2026-11-10; source updated 2026-11-10

Revision: 8471dca4c269b046790efa61c0c6c7e6b9147e828bb50df93734ea2d185da3e3

Canonical: https://y2.dev/cve/CVE-2026-104676

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.