We welcome reports from security researchers. If you believe you have found a vulnerability in WBX Sandbox, please tell us privately first and give us time to fix it before you share it with anyone else.
How to report
Email info@wbx.cz with “Security” in the subject. Please include:
- what you found and why it matters (what an attacker could do),
- steps to reproduce, with the IDs of your own test sandboxes or jobs (
sb_…,job_…), - the email address of your WBX Sandbox account, so we can credit you.
Never send us API keys or passwords. We confirm every report within 3 working days and keep you informed until it is fixed.
In scope
- The customer portal and public API at sandbox.wbx.cz, including the MCP endpoint
/mcpand OAuth. - Sandbox isolation: reaching another customer's sandbox, files, network or account; escaping the sandbox to the host; reaching our internal networks from a sandbox.
- Public sandbox addresses (
https://<port>-<sandbox>.…) and their access tokens. - Billing and credit: running sandboxes or jobs without paying, getting credit you are not entitled to.
- The official SDKs (
wbxsandboxfor Python on PyPI and for TypeScript on npm) and thewbxsandbox-mcpserver.
Rules for testing
- Test only with accounts and sandboxes you own. Do not access, change or delete data that is not yours – if you reach someone else's data, stop, do not keep a copy, and report it.
- No denial of service: no load tests, floods or attempts to exhaust shared resources (disk, memory, network) of the service. Show a resource problem with the smallest possible example.
- No spam, phishing or social engineering of our staff or customers, and no physical attacks.
- Do not use sandboxes to attack third parties – our terms of service apply to testing as well.
- Automated scanners are fine at a moderate rate; please identify yourself in the User-Agent.
Usually not eligible
- Code running inside your own sandbox with root rights – that is by design.
- Outbound internet access from a sandbox, or reaching public services from it.
- Missing security headers or best practices without a demonstrated impact; clickjacking on pages without sensitive actions; self-XSS.
- Rate limits that can only be exceeded with many accounts, and reports from automated tools without a working proof.
- Issues in third-party services we use (payment provider, email, Google or GitHub sign-in) – report those to the vendor.
Safe harbour
If you follow these rules and report in good faith, we will not take legal action against you or ask anyone else to, and we will not close your account because of the testing. If in doubt whether something is allowed, ask us first.
Rewards
We thank researchers with WBX Sandbox credit for valid, previously unknown issues. The amount depends on impact; the first reporter of an issue is rewarded. Current reward programmes are announced on our website and social channels.