Report a vulnerability
Last updated: 12 November 2026
We build security software and take every report seriously. If you think you have found a vulnerability in luviner.com, the panel or Shield, write to us: we will work with you to fix it before it becomes public.
How to report
- Email info@luviner.com with the subject "Security".
- Tell us what you found, where (URL, Shield version), steps to reproduce and the impact you expect.
- English or Italian are both fine.
What we commit to
- Acknowledge your report within 3 working days.
- Give a first assessment within 10 working days and keep you updated until it is fixed.
- Fix serious vulnerabilities as fast as possible; for Shield, fixes reach customers through the nightly automatic update.
- Agree with you when and how details are made public, normally within 90 days of the report.
- Credit you in our acknowledgements, if you wish.
- Take no legal action against anyone who reports in good faith and follows these rules.
Rules for researchers
- Do not access, modify or delete other people's data; use only your own accounts.
- No denial of service, load testing, spam or social engineering against customers or staff.
- Do not test our customers' sites protected by Shield: install Shield on your own server.
- Stop and contact us as soon as you have shown the problem, without exploiting it further.
- Do not disclose details before the issue is fixed or before the agreed date.
In scope
luviner.com and its subdomains, the customer panel, the APIs used by Shield, the Shield software and its installer.
Out of scope
Automated scanner output without demonstrated impact, missing headers without practical consequence, third-party services (Stripe, Google, CookieYes), Shield not stopping one specific bot (please tell us anyway, it helps, but it is not a vulnerability).
We do not offer monetary rewards. Our security.txt gives the same contacts in the standard format (RFC 9116).