Petpooja
Vulnerability disclosure program on security.txt petpooja.com
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 6
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report by email
- [email protected]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- No public write-ups
- Keep findings private.
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Safe harbor
-
Full
We will not pursue legal action against researchers who follow this policy.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
6 assets you may test, 14 excluded.
APIs 1
- Production APIs
Domains 1
- petpooja.com
Wildcard domains 1
- production web applications under *.petpooja.com
Products and areas 3
- Electron POS
- Official Petpooja mobile applications
- Publicly accessible production infrastructure owned by Petpooja
Out of scope (14)
- blog.petpooja.com
- Denial-of-service testing
- #dev#.petpooja.com
- Physical attacks
- Social engineering or phishing attacks
- Staging, development, QA, testing, or temporary environments
- #staging#.kharcha.com
- #staging#.petpooja.com
- #stag#.petpooja.com
- #test#.petpooja.com
- Third-party services or integrations not controlled by Petpooja
- *.petpooja.co.in
- *.petpooja.in
- *.tvito.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Petpooja's policy. "We" in these lines means the program, not this site.
While testing
-
Act in good faith
-
Avoid privacy violations and service disruption
-
Do not access or modify customer data unnecessarily
-
Provide us reasonable time to investigate and remediate reported vulnerabilities
-
If you believe your testing may exceed these guidelines, please contact us before proceeding.
Not accepted
-
Broken link hijacking (low severity)
-
Google Maps API key exposure
-
Clickjacking on pages without sensitive actions
-
CSRF on unauthenticated or non-sensitive actions
-
Attacks requiring MITM or physical device access
-
Known vulnerable libraries without a working Proof of Concept
-
CSV injection without demonstrated impact
-
SSL/TLS best-practice issues
-
Missing or weak Content Security Policy configurations
-
Missing HttpOnly or Secure cookie flags
-
Email configuration issues (SPF, DKIM, DMARC)
-
Rate-limiting or brute-force concerns
-
CDN cache invalidation or asset expiry issues
-
Software version disclosure, banners, verbose errors
-
Tabnabbing
-
Open redirects without additional exploitability
-
Self-XSS
-
Promo code or referral abuse
-
Access to publicly available user information
-
Username or email enumeration
-
Third-party platform warnings (e.g., hosting providers, CMS platforms)
-
Issues affecting outdated or unsupported browsers (more than two versions behind)
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 12 Nov 2026. Last checked 2 hours ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
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.