Citymesh Responsible Vulnerability Disclosure Program
By Citymesh Vulnerability disclosure program on Intigriti citymesh.com
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 81
- 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.
Scope
81 assets you may test, 17 excluded.
Wildcard domains 42
- *.antwerpfreewifi.be
- *.biotechnology-citymesh.com
- *.citymesh.be
- *.citymesh.com
- *.citymesh-connect.be
- *.citymeshconnect.be
- *.citymesh-connect.com
- *.citymeshconnect.com
- *.citymesh.eu
- *.citymesh.fr
- *.citymesh.guide
- *.citymesh.io
- *.citymesh.net
- *.citymesh.nl
- *.connectingsenses.be
- *.connectingsenses.com
- *.connectow.be
- *.connectow.eu
- *.ctmsh.co
- *.edpnet.be
- *.edpnet.com
- *.edpnet.net
- *.edpnet.nl
- *.engiem2m.be
- *.engiem2m.com
- *.gowifi.be
- *.myiot.be
- *.ncentric.be
- *.ncentric.cloud
- *.ncentric.com
- *.ps-radiocom.be
- *.ps-radiocom.com
- *.ptxbac.be
- *.safety-drones.be
- *.safetydrones.be
- *.safety-drones.com
- *.sigfox.nl
- *.towereye.be
- *.towereye.eu
- *.wflb.be
- *.wifilab.be
- *.wifinmbssncb.be
Networks 28
- 193.110.255.128/28
- 212.71.0.0/24
- 212.71.1.0/24
- 212.71.11.0/24
- 212.71.2.0/24
- 212.71.3.0/24
- 212.71.4.0/24
- 212.71.5.0/24
- 212.71.8.0/24
- 213.211.130.0/24
- 213.211.138.0/24
- 213.211.188.0/24
- 213.219.128.0/24
- 213.219.132.0/24
- 31.31.128.0/24
- 31.31.140.0/24
- 31.31.141.0/24
- 31.31.143.0/24
- 31.31.143.0/25
- 31.31.150.0/24
- 31.31.158.0/24
- 31.31.159.0/24
- 45.11.166.40/29
- 79.132.241.0/24
- 85.234.192.0/24
- 85.234.203.0/24
- 85.234.204.0/24
- 85.234.205.0/24
Web 11
- https://api-gateway.citymesh.com No bounty
- https://auth.citymesh.com No bounty
- https://auth.wifilab.be No bounty
- https://cabmanager.citymesh.com No bounty
- https://cc.safety-drones.com No bounty
- https://dialhome.ncentric.be No bounty
- https://extra.citymesh.com No bounty
- https://extra.edpnet.net No bounty
- https://fleet.citymeshconnect.com No bounty
- https://livechat.citymesh.com No bounty
- https://my.citymesh.com No bounty
Out of scope (17)
- 31.31.128.128/26
- 31.31.128.192/27
- 31.31.128.64/26
- 31.31.130.0/23
- 31.31.132.0/24
- 31.31.134.0/23
- 31.31.136.0/21
- 31.31.139.0/24
- 31.31.140.0-87
- 31.31.140.92-254
- 31.31.141.0/26
- 31.31.143.0-71
- *.citymesh.recruitee.com
- *.digi-mobile.be
- *.dyn.edpnet.net
- *.insky.be
- *.static.edpnet.net
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Citymesh Responsible Vulnerability Disclosure Program (via Intigriti)'s policy.
While testing
-
Respect the scope of the program
-
Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)
Not accepted
-
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
Summarised with AI from the program policy on Intigriti, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 18 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.
-
Scope removed
212.71.2.0/24
-
Scope removed
*.citymesh.com
-
Scope removed
31.31.141.0/24
-
Scope removed
*.antwerpfreewifi.be
-
Scope removed
213.219.132.0/24
-
Scope removed
*.citymesh-connect.com
-
Scope removed
*.myiot.be
-
Scope removed
*.citymesh.guide
-
Scope removed
212.71.8.0/24
-
Scope removed
*.citymesh.io
-
Scope removed
*.sigfox.nl
-
Scope removed
31.31.143.0/24
-
Scope removed
*.engiem2m.com
-
Scope removed
*.safety-drones.com
-
Scope removed
*.dyn.edpnet.net (out of scope)
-
Scope removed
*.ps-radiocom.com
-
Scope removed
*.ncentric.com
-
Scope removed
https://cc.safety-drones.com/
-
Scope removed
*.citymesh.be
-
Scope removed
https://auth.wifilab.be/
-
Scope removed
*.connectow.eu
-
Scope removed
31.31.136.0/21 (out of scope)
-
Scope removed
85.234.204.0/24
-
Scope removed
31.31.158.0/24
-
Scope removed
*.wflb.be
-
Scope removed
31.31.140.0/24
-
Scope removed
*.gowifi.be
-
Scope removed
*.biotechnology-citymesh.com
-
Scope removed
31.31.139.0/24 (out of scope)
-
Scope removed
85.234.203.0/24
-
Scope removed
*.towereye.eu
-
Scope removed
31.31.143.0-71 (out of scope)
-
Scope removed
31.31.140.0-87 (out of scope)
-
Scope removed
31.31.140.92-254 (out of scope)
-
Scope removed
*.citymesh.recruitee.com (out of scope)
-
Scope removed
31.31.159.0/24
-
Scope removed
https://my.citymesh.com/
-
Scope removed
*.towereye.be
-
Scope removed
212.71.5.0/24
-
Scope removed
https://extra.citymesh.com/
Public CVEs
Published vulnerabilities in this vendor's products, from the 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
Welcome to the Responsible Vulnerability Disclosure Program of Citymesh.
Citymesh is one of the Telecommunication Operators in Belgium. Citymesh helps its customers with the implementation, integration, and maintenance of network infrastructure. Citymesh wants to offer its customers quality connectivity solutions that help them achieve their business goals.
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)
Validation times
We will validate all submissions within the below timelines, once your submission has been verified by Intigriti. Submissions validated outside of this may be awarded a €25 bonus.
| Vulnerability Severity | Time to validate |
|---|---|
| Exceptional | 2 Working days |
| Critical | 3 Working days |
| High | 5 Working days |
| Medium | 15 Working days |
| Low | 20 Working days |
This remains at the discretion of Citymesh to award.
Check our fix We offer up to €50 bonus to verify a resolved issue for us (when requested). This remains at the discretion of Citymesh to award.
In scope
Introduction
Welcome to our Responsible Vulnerability Disclosure Program – where cybersecurity meets collaboration! We believe in the power of the community to enhance the security of our digital ecosystem. As technology advances, so do the threats, and that's why we're inviting ethical hackers, security researchers, and enthusiasts to join hands with us in identifying and resolving potential vulnerabilities.
Due to the nature of our activities, Citymesh heavily relies on information and information systems. As such, it is important that this information and / or information systems are adequately safeguarded against all known threats, both internal and external, deliberate or accidental.
Our Responsible Vulnerability Disclosure Program aims to create a secure and resilient environment for our users by encouraging responsible disclosure of security issues. We value the expertise and creativity of the security community and are committed to fostering a transparent and cooperative relationship with those who help us strengthen our defenses.
Our worst-case scenarios are:
- Disclosure of PII
- RCE & privilege escalation
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
- 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
- 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
Severity
This program follows Intigriti's triage standards
FAQ
Where can we get credentials for the app?
We currently don’t offer any credentials to test user roles.
If you have any questions at all, feel free to contact us through the support team of Intigriti.