How to fix passive scan only on Wix

Steps for Wix

1. Wix does not offer a server-level staging environment; use the built-in 'Dev Mode' preview or duplicate your site: Site → Duplicate Site from the dashboard to create a test copy.
2. On the duplicate site, keep it unpublished (it will have a wix.com subdomain that is not indexed).
3. Because Wix is a fully managed SaaS platform, deep server-level DAST is limited — focus on scanning your published site's externally accessible endpoints (login, contact forms, Wix Stores checkout) using OWASP ZAP in passive/spider mode against the duplicate's preview URL.
4. For any custom Velo (Wix Code) backend functions, review them manually against the OWASP Cheat Sheet for input validation and authentication.
5. Report significant findings to Wix Support or disable vulnerable third-party apps from Add Apps → Manage Apps.
6. Keep all Wix apps updated; most security fixes on the core platform are handled automatically by Wix.

What is passive scan only?

Passive security scans — like the checks run on your HTTP headers, TLS certificate, cookies, and email DNS records — are a great first step, but they can only see what your store broadcasts to any visitor. They cannot test whether your login form is vulnerable to brute-force attacks, whether your checkout accepts malicious input, or whether an authenticated user can access another customer's data. Active security testing (called DAST — Dynamic Application Security Testing) actually interacts with your live or staging site the way a real attacker would, probing for those deeper vulnerabilities. Tools like OWASP ZAP (free) or commercial equivalents send crafted requests to your store and report weaknesses that a passive scan will never find.

A security breach on an ecommerce store can expose customer payment data, personal information, and order history — leading to regulatory fines (GDPR, PCI DSS), chargebacks, loss of payment processor access, and permanent damage to customer trust. Many of the most damaging attack types — SQL injection, cross-site scripting (XSS), broken authentication, insecure direct object references — are invisible to passive scanning but are caught routinely by DAST tools. Running active tests before each release means you find and fix vulnerabilities before attackers do, protecting your revenue, your customers, and your brand reputation. Skipping this step is one of the top reasons stores appear in breach reports despite having "green" passive security scores.

See the complete Passive scan only guide for every platform and the full background.