Zabka Group Vulnerability Disclosure Program
By Żabka Group Vulnerability disclosure program on Intigriti zabka.pl
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 10
- 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
We do not offer any rewards in our Vulnerability Disclosure Program.
Summarised with AI from the program policy on Intigriti, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
10 assets you may test, 6 excluded.
Web 8
- https://delio.com.pl
- https://dietly.pl
- https://jush.pl
- https://lite.tech
- https://maczfit.pl
- https://masterlifecrm.com
- https://zabkagroup.com
- https://zabka.pl
Wildcard domains 1
- *.zabka.pl
Products and areas 1
- Mobile applications
Out of scope (6)
- 195.94.213.80 - 195.94.213.95
- 217.153.50.112 - 217.153.50.127
- Żabka Nano stores
- https://foodziki.zabka.pl
- zabka-snrs.zabka.pl
- *.zabka-snrs.zabka.pl
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Zabka Group Vulnerability Disclosure Program (via Intigriti)'s policy. "We" in these lines means the program, not this site.
While testing
-
Please be gentle. If you notice that your tests may have impact on the service please lower request rate. It is especially important between 3 am and 1 pm GMT.
-
If you suspect that your actions may caused some damage, please stop, report steps already taken and wait for our permission to continue.
-
Please do not scan automatically. Keep request rate below 3 req/s
-
Do not modify any data
-
Do not intentionally access and/or download any peronal data of our customers or employees. If accidentally access any of those, stop and immediately report the finding.
-
Respect the scope of the program
-
Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)
-
Please do not scan our public IP range
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, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 57 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
https://dietly.pl
-
Scope removed
zabka-snrs.zabka.pl (out of scope)
-
Scope removed
195.94.213.80 - 195.94.213.95 (out of scope)
-
Scope removed
*.zabka-snrs.zabka.pl (out of scope)
-
Scope removed
217.153.50.112 - 217.153.50.127 (out of scope)
-
Scope removed
Mobile applications
-
Scope removed
https://maczfit.pl
-
Scope removed
https://lite.tech
-
Scope removed
https://zabka.pl
-
Scope removed
*.zabka.pl
-
Scope removed
https://jush.pl
-
Scope removed
Żabka Nano stores (out of scope)
-
Scope removed
https://delio.com.pl
-
Scope removed
https://foodziki.zabka.pl (out of scope)
-
Scope removed
https://masterlifecrm.com
-
Scope removed
https://zabkagroup.com
-
Scope removed
195.94.213.80 - 195.94.213.95
-
Scope removed
217.153.50.112 - 217.153.50.127
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
Żabka Group is the ultimate convenience ecosystem that aims to make people’s lives easier. We accompany consumers at every moment of the day, freeing up their time through the possibility of convenient grocery shopping, have a hot meal on the go, send a package, withdraw cash or take advantage of a dietary catering with delivery.
We are aware, that despite our greatest efforts, our knowledge may not be sufficent to keep us safe. Therefore we started our vulnerability disclosure program because we believe that working closely with skilled security researchers is beneficial to for all parties.
Rules of engagement
Rules:
- Please be gentle. If you notice that your tests may have impact on the service please lower request rate. It is especially important between 3 am and 1 pm GMT.
- If you suspect that your actions may caused some damage, please stop, report steps already taken and wait for our permission to continue.
- Please do not scan automatically. Keep request rate below 3 req/s
- Do not modify any data
- Do not intentionally access and/or download any peronal data of our customers or employees. If accidentally access any of those, stop and immediately report the finding.
- 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)
In scope
Introduction
Here at Zabka Group we take security very seriously. We are aware, that despite our greatest efforts, our knowledge may not be sufficient to keep us safe. Therefore we invite you, to help us because we believe that working closely with skilled security researchers is beneficial for all parties.
We do not offer any rewards in our Vulnerability Disclosure Program. For selected assets we run a private Bug Bounty program. Reports submitted to VDP will not qualify for bug bounty programs.
Priorities
We are specifically interested in:
- Leaking of personal data
- Privileges escalation
- Remote code execution
- SQL injection
Out of scope
Domains
- zabka-snrs.zabka.pl and all it's subdomains
- domains used by mobile apps which are not subdomains of any of in-scope domains
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
- Please do not scan our public IP range
- 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 mobile apps?
You can self-register to some of our apps (Zappka, Dielty, Maczfit, Jush). Unfortunately, we do not offer test credentials for the rest of our applications.
Why do i get 403 response
We do have a WAF in front of some of our endpoints. Please lower the rate of requests sent.