Wix and Velo Security Review
A Wix site’s Velo backend functions and Data collections are only as private as the permission level set on them. We test those permissions, not Wix’s own platform. CREST-certified testers, fixed price from £2,080 for a 2-day single-site scope, quoted within 24 hours.
- Unlimited retesting
- Unlimited pre-retesting
- No hidden fees
“I would highly recommend EJN Labs to any organisation seeking reliable, detailed, and well-managed penetration testing services, particularly for government or enterprise-level projects.”
“There wasn’t another company we could find that could deliver what we needed in the timeframe we needed. The client loved it, and we got instant ROI from the engagement.”
Every Velo backend function and Data collection ships with a permission level, Anyone, Site Member or Admin, that the developer chooses. We test whether the level actually set matches what the function or collection should allow.
Why Velo permissions, not Wix’s platform, decide what a site exposes
Velo’s backend web modules keep their code hidden from the browser, but Wix’s own developer documentation is explicit that any exported function can still be called by anyone who can reach it, with whatever arguments they choose, unless its permission is set to Site Members or Admin. We test every exported function against the permission it was actually given, and what it does with an argument the front end was never built to send.
Wix Data collections carry their own read and write permission settings, independent of the pages that happen to use them, so a collection built for one form can end up reachable directly through the Data API from a page that never intended to expose it. We test what a visitor, a logged-in member and an admin account can each read, insert or remove through every collection in scope, rather than only through the forms the site’s designer built.
Backend code reads credentials through Velo’s Secrets Manager, which keeps each value encrypted and off the client, and a separate http-functions.js file can expose a custom endpoint on the site’s own domain simply by naming a function get_ or post_ followed by its path. We test whether a secret ever reaches a response the client can see, and what an http-functions.js endpoint returns to a request it was not designed to authenticate.
SCOPE
What we pen test on a Wix and Velo site
Web Module Function Permissions
Every exported web module function carries a permission level, Anyone, Site Members or Admin, set independently per function rather than per file. We test each exported function against the permission it was actually given, not the one its name or folder suggests.
Backend Function Input Validation
Wix’s own documentation warns that any function callable from the front end can be called by anyone with any arguments, whether or not the intended UI would ever send them. We test what a backend function does with an argument, a missing field or an unexpected type it was never built to validate.
Data Collection Read Permissions
A collection’s read permission, Anyone, Site Member or Admin, decides what wix-data queries running in page code can return, independently of whichever form or repeater the designer connected to it. We test whether a collection meant for members-only data is still readable by an anonymous visitor through a direct query.
Data Collection Write Permissions
Write permission on a collection is set separately from read permission, so a collection open for anyone to read can still block writes, or the reverse. We test insert, update and remove access on every collection in scope against the role that should actually hold it.
Members Area and Member-Only Pages
Pages set to members-only are meant to be reachable only by a signed-in site member, but that restriction sits in the page’s own settings rather than in the data a page’s backend calls might still return. We test whether a member-only page’s content, and the collections or functions it calls, are hidden from a visitor who is not signed in.
http-functions.js Endpoint Exposure
An http-functions.js file exposes a custom HTTP endpoint on the site’s own domain the moment a function is named get_, post_ or use_ followed by its path, with no permission setting of its own. We test what each exposed endpoint returns to an unauthenticated request, since Velo does not gate these functions the way it gates web module permissions.
Secrets Manager Usage
Backend code reads API keys and other credentials through the Secrets Manager rather than hardcoding them, keeping the value itself off the client. We test whether a secret referenced through wix-secrets-backend ever reaches a log, an error message or a response the browser can read.
Third-Party Integrations and API Keys
A Wix site calling a payment provider, CRM or marketing platform from backend code depends on that integration’s own credentials and webhook handling being correct, on top of Velo’s own permission model. We test the integration boundary itself, including whether a webhook endpoint validates the request it receives before acting on it.
Client-Side Code and Page Elements
Frontend Velo code and page elements run in the visitor’s browser, so any logic, validation or reference to an internal field name written there is visible to anyone who opens the page source. We check what frontend code and $w element properties expose about the site’s backend structure.
No-Code Site Estate Beyond Wix
Where your organisation runs a Wix site alongside a Webflow site for a different property or campaign, our Webflow security review covers that platform on its own terms rather than assuming Velo’s permission model applies there too.
OUR PROCESS
Wix and Velo Application Security Review: From Scope to Attestation
Scope and Access
We agree the pages, collections, web modules and http-functions endpoints in scope, and you provide a member account and an editor or admin login where backend code and collection permissions need reviewing.
Permission and Endpoint Mapping
We map every web module function, collection and http-functions endpoint against the permission level it was actually given.
Manual Testing
A CREST-certified tester manually tests permission bypass, endpoint exposure, secrets handling and member-only access, chaining findings where they compound.
Attestation and Retest
You get a technical report with CVSS scores and reproduction steps, a walkthrough call, a free retest once fixes are deployed, and an attestation letter for auditors.
CREDENTIALS
Verified Accreditations Auditors Accept
Every credential below is independently verifiable. UK procurement teams, FCA supervisors, ISO 27001 / SOC 2 auditors, and cyber insurance underwriters all recognise these standards.
GET YOUR QUOTE
Get a CREST Wix pen test quote in 24 hours
A fixed-price quote back in one business day, from a named CREST assessor. No sales pipeline, no chasing.
- CREST and IASME accredited. Testing your auditors and clients already recognise.
- Fast-track testing within 24 hours where required. Free retest of every fix included.
- Live findings via your client portal, not a four-week PDF.
- Fixed price from £3,500 for a single-role, single-app scope, agreed up front. Most engagements run £5,000 and up. No day-rate surprises.
Dan WilcocksonFounder, CelloriUnder NDA Further named references available on a scoping call.
- We reply within one business day with a fixed-price quote from a named CREST assessor.
- You approve the scope and we book a start date, usually within 24 hours.
- Live findings land in your client portal as we test, with a free retest of every fix.
Get your fixed pen test quote in 24 hours
Quote request received
We will reply within one business day with your fixed-price quote from a named CREST assessor.
Your data stays with us. No newsletter signup.
or book a 20-min scoping call first
We reply within one business day. Your data stays with us. No newsletter signup.
COMPLIANCE READY
Reports Mapped to Every Framework
Findings are written so your team can reference the report against each framework without translation work.
ISO 27001:2022
Annex A.8.8 management of technical vulnerabilities plus A.5.15-5.18 and A.8.2-8.5 access control validation.
SOC 2 Type I & II
CC6 logical access, CC7 system operations, CC8 change management evidence.
PCI DSS
Requirement 11.4 application penetration testing across cardholder data environments, including ecommerce penetration testing for online retail platforms.
FCA SYSC
SYSC 4.1.1R, 6.1.1R, 13 mapped to each finding for FCA-regulated firms.
UK GDPR
Article 32 effectiveness testing, customer-data security controls, ICO-acceptable evidence.
Cyber Essentials Plus
Direct certification through our IASME body status, single-vendor delivery.
PRICING
Transparent Wix and Velo Application Security Review Pricing
Pricing depends on the number of roles, integrations and environments in scope. See our pricing page for how we quote.
1 to 2 testing days
Single user role, basic CRUD application, marketing website with auth. Around 5 working days from kickoff to report.
Get a fixed quote2 to 3 testing days
Multi-role SaaS, business application with payment integration. Around 8 to 12 working days from kickoff to report.
Get a fixed quote3 to 5 testing days
Multi-tenant platform, complex authorisation matrix, integration-heavy applications. Around 15 to 20 working days from kickoff to report.
Get a fixed quoteSECTORS
Sectors We Test Wix For
Sector-specific scoping for regulated UK organisations.
Fintech & FCA-Regulated
FCA SYSC, Open Banking FAPI 1.0, PSD2 SCA, payment-flow scrutiny, KYC/AML testing.
Fintech sector pageSaaS Companies
SOC 2 Type I & II evidence, multi-tenant boundaries, role escalation, customer-tenant isolation.
SaaS sector pageLaw Firms
SRA Cyber Standard, privileged data, conveyancing fraud defence, partner-tier procurement.
Law firm sector pageHealthcare
NHS DTAC, DSP Toolkit v6, UK GDPR Article 32, EHR systems, telehealth platforms.
Healthcare sector pageInsurance
FCA / PRA Operational Resilience, cyber underwriting, claims data, broker portals.
Insurance sector pagePublic Sector
CCS / G-Cloud framework, NCSC-aligned, citizen-facing services, PSN-compliance scrutiny.
Public sector pageWHY EJN LABS
What You Get From Wix and Velo Application Security Review
Six concrete differentiators competitors don’t all match.
CREST-Certified Testers, Verifiable
Every test by a CREST-certified pen tester (CRT, CCT APP, CCT INF where applicable). Verify our company status at crest-approved.org.
24-Hour Startup, Where Required
From signed scope to active testing in a single business day for incident response, audit deadlines, or regulator-driven timelines.
Live Findings, Not 4-Week PDFs
Critical issues reported during testing through your client portal. Your team remediates while testing continues.
Audit-Ready Reports
Executive summary plus full technical report with CVSS scores and explicit framework mappings (ISO 27001, SOC 2, PCI DSS, FCA SYSC).
Free Retests, Standard
Verify remediation of every finding before close-out. Letter of attestation for audit submission included. Most competitors charge £1,500-£3,000 per retest.
UK-Based CREST Testers
Every engagement performed by vetted, UK-based CREST-certified testers, matched to your needs, security clearance, and compliance scope.
FAQ
Frequently Asked
What access do you need to test our Wix site?
We need the site URL and a signed-in member account for any member-only content. Where backend code and collection permissions are in scope, an editor or admin login to the Wix Editor speeds up mapping every web module, collection and http-functions endpoint we need to test.
Will testing touch our live data?
We test whichever environment you give us access to. If that is your live site, we agree exclusions upfront, such as real form submissions or payment processing, and we do not run destructive tests against real customer records without that agreement in writing.
How long does a Wix and Velo security review take?
A single site sits in our 2-day single-site scope, with a report typically landing around 5 working days after kickoff. A site with several web modules, custom http-functions endpoints or multiple third-party integrations moves into a wider scope with more testing days.
Is a Wix site without custom Velo code still worth testing?
Yes. Members Area configuration, collection permissions used by native Wix apps, and third-party integrations connected through the platform’s own settings are still worth testing even where a site has no custom backend code of its own.
What is out of scope for a Wix and Velo security review?
Wix’s own shared platform and infrastructure are out of scope; we review your site’s code, pages and collection permissions, never Wix’s underlying service. A separate application your site integrates with, rather than the site itself, is scoped and quoted separately.
Do you need our source code?
No. Testing is black-box against the live site by default. A grey-box option, where we review the relevant web module code and collection permission configuration in the Wix Editor alongside testing, is available if you want faster or deeper coverage of specific findings.
Does Wix have a customer penetration-testing policy we need to follow?
We review your site’s own code, pages and collection permissions rather than Wix’s shared infrastructure, which is out of scope for any customer test. Where testing needs to reach further into Wix-operated infrastructure, we confirm Wix’s current testing terms during scoping.
20+ CREST-accredited testing services in one place
Web, mobile, API, cloud, AI, infrastructure, red team. Pick the test that fits your environment.
Get a fixed price for your Wix and Velo site
A Wix site’s Velo backend functions and Data collections are only as private as the permission level set on them. We test those permissions, not Wix’s own platform. CREST-certified testers, fixed price from £2,080 for a 2-day single-site scope, quoted within 24 hours.
