Skip to content

Orbia Responsible Disclosure

By Orbia Vulnerability disclosure program on Intigriti orbia.com

Accepting reports Full safe harbor
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
31
Public CVEs
0
Last change

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report on Intigriti
Submit through the program page.
Full safe harbor
Good-faith research is authorised; no legal action.
No public write-ups
Keep findings private.

Rewards

What Intigriti lists as the payout for each severity.

This program does not pay cash rewards.

Pays cash
No This vulnerability disclosure program is currently not offering rewards.

Summarised with AI from the program policy on Intigriti, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

31 assets you may test, 3 excluded.

Wildcard domains 24

  • *.alphagary.com
  • *.alphagarycompuestos.com
  • *.amanco.com
  • aqora.naiad.*
  • *.biarrinetworks.com
  • *.bow-group.com
  • *.duraline.com
  • *.klea.com
  • *.kouraglobal.com
  • *.metropolder.com
  • *.mexichem.com
  • *.naiad.cloud
  • *.naiad.ninja
  • *.netafim.com
  • *.orbia.com
  • *.orbiaglobal.com
  • *.plastigama.com
  • *.polderroof.com
  • *.silatronix.com
  • *.sylvin.com
  • *.vestolit.com
  • *.wavin.com
  • *.wavin.io
  • *.zephex.com

Android apps 4

  • br.com.ideia2001.CatalogoWavin
  • com.instalsoft.wavinsmartinstalsystem
  • com.RD3Digital.AmancoWavinRA
  • com.wavin.sentio

iOS apps 3

  • 1383688497
  • 1517825382
  • 1616009566
Out of scope (3)
  • com.loyaltyworks.wavinapp
  • 1584170510
  • *.vectus.in

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Orbia Responsible Disclosure (via Intigriti)'s policy. "We" in these lines means the program, not this site.

While testing

  • Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)
  • Make sure that during your investigation you do not cause any damage or disruptions to our systems so do not alter, change or delete data from our systems.
  • Do not put a backdoor in the system, not even for the purpose of showing the vulnerability
  • do not penetrate the system any further than required for the purpose of your investigation.
  • Do not access unnecessary, excessive or significant amount of data including disrupting any services or systems.
  • Make sure that during your research you do not inadvertently cause a data breach (i.e. sharing screenshots or recordings on 3rd party cloud solution).
  • If you self-register for any accounts, please register with your @intigriti.me email address.
  • Reports are required to be written in English.

Not accepted

  • API key disclosure without proven business impact
  • Wordpress usernames disclosure
  • Pre-Auth Account takeover/OAuth squatting
  • Self-XSS that can't be used to exploit other users
  • Verbose messages/files/directory listings without disclosing any sensitive information
  • CORS misconfiguration on non-sensitive endpoints
  • Missing cookie flags
  • Missing security headers
  • Cross-site Request Forgery with no or low impact
  • Presence of autocomplete attribute on web forms
  • Reverse tabnabbing
  • Bypassing rate-limits or the non-existence of rate-limits.
  • Best practices violations (password complexity, expiration, re-use, etc.)
  • Clickjacking without proven impact/unrealistic user interaction
  • CSV Injection
  • Sessions not being invalidated (logout, enabling 2FA, etc.)
  • Tokens leaked to third parties
  • Anything related to email spoofing, SPF, DMARC or DKIM
  • Content injection without being able to modify the HTML
  • Username/email enumeration
  • Email bombing
  • HTTP Request smuggling without any proven impact
  • Homograph attacks
  • XMLRPC enabled
  • Banner grabbing/Version disclosure

Summarised with AI from the program policy on Intigriti, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 46 minutes ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Before we tracked it

Scope and reward changes recorded before this page started tracking it.

  1. Scope removed

    *.silatronix.com

  2. Scope removed

    br.com.ideia2001.CatalogoWavin

  3. Scope removed

    com.RD3Digital.AmancoWavinRA

  4. Scope removed

    *.zephex.com

  5. Scope removed

    *.naiad.cloud

  6. Scope removed

    *.duraline.com

  7. Scope removed

    *.polderroof.com

  8. Scope removed

    *.plastigama.com

  9. Scope removed

    *.alphagary.com

  10. Scope removed

    *.mexichem.com

  11. Scope removed

    *.bow-group.com

  12. Scope removed

    *.metropolder.com

  13. Scope removed

    *.wavin.com

  14. Scope removed

    *.kouraglobal.com

  15. Scope removed

    1584170510 (out of scope)

  16. Scope removed

    1517825382

  17. Scope removed

    1383688497

  18. Scope removed

    1616009566

  19. Scope removed

    com.wavin.sentio

  20. Scope removed

    com.loyaltyworks.wavinapp (out of scope)

  21. Scope removed

    com.instalsoft.wavinsmartinstalsystem

  22. Scope removed

    aqora.naiad.*

  23. Scope removed

    *.orbia.com

  24. Scope removed

    *.orbiaglobal.com

  25. Scope removed

    *.vestolit.com

  26. Scope removed

    *.amanco.com

  27. Scope removed

    *.sylvin.com

  28. Scope removed

    *.biarrinetworks.com

  29. Scope removed

    *.vectus.in (out of scope)

  30. Scope removed

    *.netafim.com

  31. Scope removed

    *.naiad.ninja

  32. Scope removed

    *.alphagarycompuestos.com

  33. Scope removed

    *.wavin.io

  34. Scope removed

    *.klea.com

  35. Scope added

    Aqora.*

  36. Scope removed

    1584170510

  37. Scope removed

    com.instalsoft.wavinsmartinstalsystem

  38. Scope removed

    aqora.naiad.*

  39. Scope removed

    1616009566

  40. Scope removed

    com.RD3Digital.AmancoWavinRA

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.

Original policy

Copied from www.intigriti.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Description

Orbia is a purpose-led manufacturing group of companies, passionate about the challenges that define how people will live and thrive tomorrow to deliver strategic, collaborative, and human-centered solutions. As part of our commitment to security, we invite researchers to participate in the disclosure program, helping us ensure protection of our systems.

Join us in identifying and reporting vulnerabilities to maintain the highest standards of security for our customers and partners.

Rules of engagement

By participating in this program, you agree to:

  • Respect the Community Code of Conduct
  • Respect the Intigriti Terms and Conditions
  • Respect the scope of the program
  • Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)

Reports are required to be written in English. Please include a clear attack scenario outlining detailed reproduction steps.

Make sure that during your investigation you do not cause any damage or disruptions to our systems so do not alter, change or delete data from our systems.

Do not put a backdoor in the system, not even for the purpose of showing the vulnerability as inserting a backdoor will cause even more damage to the safety of our systems and do not penetrate the system any further than required for the purpose of your investigation.

Do not access unnecessary, excessive or significant amount of data including disrupting any services or systems.

Make sure that during your research you do not inadvertently cause a data breach (i.e. sharing screenshots or recordings on 3rd party cloud solution).

No credentials are provided for this program. If you self-register for any accounts, please register with your @intigriti.me email address.

Check our fix We offer up to €50 bonus to verify a resolved issue for us. This remains at the discretion of Orbia to award

In scope

We are happy to announce our Responsible Disclosure program!

This vulnerability disclosure program is currently not offering rewards.

Priorities

We are interested to learn about any potential vulnerabilities that could impact the security and privacy of our systems or customers. In addition to the above scope, this program applies to any assets associated with Orbia and business groups services, products or web properties. We are specifically looking for:

  • Horizontal / vertical privilege escalation
  • Unauthorized modification or deletion of sensitive data
  • Lateral movement
  • Authentication bypass methods
  • Security Misconfigurations
  • Data Breach
  • Injection or RCE
  • ....

We plan to update our scope periodically so keep an eye on us or subscribe to our program to receive updates when we do!

Feedback Would you like to help us improve our program or have some feedback to share, please send your anonymous feedback here:

Program feedback link Please note this form will be checked periodically and should not be used for submission or support queries.

Out of scope

Application

  • API key disclosure without proven business impact
  • Wordpress usernames disclosure
  • Pre-Auth Account takeover/OAuth squatting
  • Self-XSS that can't be used to exploit other users
  • Verbose messages/files/directory listings without disclosing any sensitive information
  • CORS misconfiguration on non-sensitive endpoints
  • Missing cookie flags
  • Missing security headers
  • Cross-site Request Forgery with no or low impact
  • Presence of autocomplete attribute on web forms
  • Reverse tabnabbing
  • Bypassing rate-limits or the non-existence of rate-limits.
  • Best practices violations (password complexity, expiration, re-use, etc.)
  • Clickjacking without proven impact/unrealistic user interaction
  • CSV Injection
  • Sessions not being invalidated (logout, enabling 2FA, etc.)
  • Tokens leaked to third parties
  • Anything related to email spoofing, SPF, DMARC or DKIM
  • Content injection without being able to modify the HTML
  • Username/email enumeration
  • Email bombing
  • HTTP Request smuggling without any proven impact
  • Homograph attacks
  • XMLRPC enabled
  • Banner grabbing/Version disclosure
  • Not stripping metadata of files
  • Same-site scripting
  • Subdomain takeover without taking over the subdomain
  • Arbitrary file upload without proof of the existence of the uploaded file
  • Blind SSRF without proven business impact (pingbacks aren't sufficient)
  • Disclosed/misconfigured Google Maps API keys
  • Host header injection without proven business impact

General

  • Theoretical vulnerabilities without any proof or demonstration of the real presence of the vulnerability (e.g.: Subdomain Takeovers without proof of actually taking over the subdomain).
  • Findings from automated tools without providing a Proof of Concept.
  • In case that a reported vulnerability was already known to the company from their own tests, it will be flagged as a duplicate
  • Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited
  • Spam, social engineering and physical intrusion
  • DoS/DDoS attacks or brute force attacks
  • Vulnerabilities that only work on software that no longer receive security updates
  • Attacks requiring physical access to a victim's computer/device, man in the middle or compromised user accounts
  • Recently discovered zero-day vulnerabilities found in in-scope assets within 14 days after the public release of a patch or mitigation may be reported, but are usually not eligible for a bounty
  • Reports that state that software is out of date/vulnerable without a proof-of-concept

Mobile

  • Shared links leaked through the system clipboard
  • Any URIs leaked because a malicious app has permission to view URIs opened
  • The absence of certificate pinning
  • Sensitive data in URLs/request bodies when protected by TLS
  • Lack of obfuscation
  • Path disclosure in the binary
  • Lack of jailbreak & root detection
  • Crashes due to malformed URL Schemes
  • Lack of binary protection (anti-debugging) controls, mobile SSL pinning
  • Snapshot/Pasteboard leakage
  • Runtime hacking exploits (exploits only possible in a jailbroken environment)
  • API key leakage used for insensitive activities/actions

Severity

This program follows Intigriti's triage standards

FAQ

Where can we get credentials for the app?

You can self-register on the application where applicable but please don’t forget to use your @intigriti.me address.

Where can we get credentials for the app?

We currently don’t offer any credentials to test user roles. Feel free to reach out to support if you have any issue with this.