- Top reward
- €1,000
- Top severity paid
- Critical
- Assets in scope
- 22
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- Pays up to €1,000
- for critical bugs.
- Report on YesWeHack
- Submit through the program page.
- No public write-ups
- Keep findings private.
Rewards
What YesWeHack lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
€2,500 |
| High |
|
€1,000 |
| Medium |
|
€300 |
| Low |
|
€50 |
Scope
22 assets you may test, 1 excluded.
Web 17
- analytics.pinelabs.com
- dashboard.pluralonline.com
- https://billingserver.pinelabs.com
- https://board.pinelabs.com
- https://credit.pinelabs.com
- https://emistores.pinelabs.com
- https://lounge.pinelabs.com/loungeui/login
- https://myplutus.pinelabs.my
- https://nbs.pinelabs.com
- https://pinepgconsole.in:9099
- https://trm.pinelabs.ae
- https://www.letspaylater.ph
- https://www.pinelabs.ae
- https://www.pinelabs.com
- https://www.pinelabs.my
- https://www.pinelabs.us
- trm.pinepaymentsolutions.com
APIs 4
- https://api.pluralonline.com
- https://api.pluralpay.in
- https://pinepg.in
- https://pluralcheckout.pinepg.in
Android apps 1
- https://play.google.com/store/apps/details?id=com.pinelabs.emicatalogue.pinelabs&hl=uz
Out of scope (1)
- All other Pine Labs assets that are not listed above are to be treated as out of scope
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Pine Labs Bug Bounty Program (via YesWeHack)'s policy. "We" in these lines means the program, not this site.
While testing
-
Denial of service (DoS) attacks on Pine Labs applications, servers, networks or infrastructure are strictly forbidden.
-
Avoid tests that could cause degradation or interruption of our services.
-
Do not use automated scanners or tools that generate large amount of network traffic.
-
Only perform tests against your own accounts to protect our users' privacy.
-
Do not leak, manipulate, or destroy any user data or files in any of our applications/servers.
-
Do not copy any files from our applications/servers and disclose them.
-
No vulnerability disclosure, full, partial or otherwise, is allowed.
-
You must not be a former or current employee of Pine Labs or one of its contractors.
Not accepted
-
Broken Link/Social media Hijacking
-
Tabnabbing
-
Missing cookie flags
-
Content/Text injections
-
Clickjacking/UI redressing
-
Denial of Service (DoS) attacks
-
Recently disclosed CVEs (less than 45 days sinces patch release)
-
CVEs without exploitable vulnerabilities and PoC
-
Open ports or services without exploitable vulnerabilities and PoC
-
Social engineering of staff or contractors
-
Presence of autocomplete attribute on web forms
-
Vulnerabilities affecting outdated browsers or platforms
-
Self-XSS or XSS that cannot be used to impact other users
-
Any hypothetical flaw or best practices without exploitable vulnerabilities and PoC
-
SSL/TLS issues (e.g. expired certificates, best practices)
-
Unexploitable vulnerabilities (e.g. Self-XSS, XSS or Open Redirect through HTTP headers...)
-
Reports with attack scenarios requiring MITM or physical access to victim's device
-
Missing security-related HTTP headers which do not lead directly to an exploitable vulnerability and PoC
-
Low severity Cross-Site Request Forgery (CSRF) (e.g. Unauthenticated / Logout / Login / Products cart updates...)
-
Invalid or missing email security records (e.g. SPF, DKIM, DMARC)
-
Session management issues (e.g. lack of expiration, no logout on password change, concurrent sessions)
-
CSV injection
-
Malicious file upload (e.g. EICAR files, .EXE)
-
HTTP Strict Transport Security Header (HSTS)
Summarised with AI from the program policy on YesWeHack, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 5 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://developers.woohoo.in/
-
Scope removed
https://www.woohoo.in/
-
Scope added
All other Pine Labs assets that are not listed above are to be treated as out of scope (out of scope)
-
Scope added
https://lounge.pinelabs.com/loungeui/login
-
Scope added
https://plmcixt.pinelabs.com
-
Scope added
https://pluralcheckout.pinepg.in
-
Scope added
https://pinepg.in
-
Scope added
https://api.pluralpay.in
-
Scope added
https://api.pluralonline.com
-
Scope added
https://nbs.pinelabs.com
-
Scope added
https://board.pinelabs.com
-
Scope added
https://www.pinelabs.us
-
Scope added
https://www.pinelabs.ae
-
Scope added
https://www.pinelabs.my
-
Scope added
https://www.pinelabs.com
-
Scope added
https://emistores.pinelabs.com
-
Scope added
https://play.google.com/store/apps/details?id=com.pinelabs.emicatalogue.pinelabs&hl=uz
-
Scope added
https://credit.pinelabs.com
-
Scope added
https://www.letspaylater.ph
-
Scope added
https://trm.pinelabs.ae
-
Scope added
trm.pinepaymentsolutions.com
-
Scope added
https://myplutus.pinelabs.my
-
Scope added
analytics.pinelabs.com
-
Scope added
https://pinepgconsole.in:9099
-
Scope added
dashboard.pluralonline.com
-
Scope added
https://billingserver.pinelabs.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 yeswehack.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Rules
Pine Labs
Pine Labs is an Indian merchant platform company that provides financing and last-mile retail transaction technology, founded in 1998. It is one of the unicorn companies, with a valuation of over US$5 billion. It provides a merchant platform and makes software for point of sale machines.
Program Rules
At Pine Labs we recognize the important role that security researchers play in helping to keep Pine Labs and our customers secure.
By participating in this program you acknowledge that you have read and agreed to the Program Rules, which is defined as this entire document.
Testing Policy and Responsible Disclosure
Please adhere to the following rules while performing research on this program:
- Denial of service (DoS) attacks on Pine Labs applications, servers, networks or infrastructure are strictly forbidden.
- Avoid tests that could cause degradation or interruption of our services.
- Do not use automated scanners or tools that generate large amount of network traffic.
- Only perform tests against your own accounts to protect our users' privacy.
- Do not leak, manipulate, or destroy any user data or files in any of our applications/servers.
- Do not copy any files from our applications/servers and disclose them.
- No vulnerability disclosure, full, partial or otherwise, is allowed.
Reward Eligibility and Amount
We are happy to thank everyone who submits valid reports which help us improve the security of Pine Labs, however only those that meet the following eligibility requirements may receive a monetary reward:
- You must be the first reporter of a vulnerability.
- The vulnerability must be a qualifying vulnerability (see below).
- The report must contain the following elements:
- Clear textual description of the vulnerability, how it can be exploited, the security impact it has on the application, its users and Pine Labs, and remediation advice on fixing the vulnerability
- Proof of exploitation: screenshots and/or videos demonstrating the exploit was performed, and showing the final impact
- Provide complete steps with the necessary information to reproduce the exploit, including (if necessary) code snippets, payloads, commands etc
- You must not break any of the testing policy rules listed above
- You must not be a former or current employee of Pine Labs or one of its contractors.
Reward amounts are based on:
- Reward grid of the report's scope
- CVSS scoring and actual business impact of the vulnerability upon performing risk analysis
Out of scope
- All other Pine Labs assets that are not listed above are to be treated as out of scope
Qualifying vulnerabilities
- SQL Injection (SQLi)
- Cross-Site Scripting (XSS)
- Remote Code Execution (RCE)
- Insecure Direct Object Reference (IDOR)
- Horizontal and vertical privilege escalation
- Authentication bypass & broken authentication
- Business Logic Errors vulnerability with real security impact
- Local files access and manipulation (LFI, RFI, XXE, SSRF, XSPA)
- Cross-Origin Resource Sharing (CORS) with real security impact
- Cross-site Request Forgery (CSRF) with real security impact
- Open Redirect
- Sensitive Information Exposure Through insecure data storage on device
- Leaked information from Mobile (without rooting)
- Insecure Communication
- Insecure Authentication
- Insecure Authorization
- Insufficient Cryptography
- Hardcoded secrets
- Exposed secrets, credentials or sensitive information on an asset under our control and affecting at least one of our scopes
Non-qualifying vulnerabilities
- Broken Link/Social media Hijacking
- Tabnabbing
- Missing cookie flags
- Content/Text injections
- Clickjacking/UI redressing
- Denial of Service (DoS) attacks
- Recently disclosed CVEs (less than 45 days sinces patch release)
- CVEs without exploitable vulnerabilities and PoC
- Open ports or services without exploitable vulnerabilities and PoC
- Social engineering of staff or contractors
- Presence of autocomplete attribute on web forms
- Vulnerabilities affecting outdated browsers or platforms
- Self-XSS or XSS that cannot be used to impact other users
- Any hypothetical flaw or best practices without exploitable vulnerabilities and PoC
- SSL/TLS issues (e.g. expired certificates, best practices)
- Unexploitable vulnerabilities (e.g. Self-XSS, XSS or Open Redirect through HTTP headers...)
- Reports with attack scenarios requiring MITM or physical access to victim's device
- Missing security-related HTTP headers which do not lead directly to an exploitable vulnerability and PoC
- Low severity Cross-Site Request Forgery (CSRF) (e.g. Unauthenticated / Logout / Login / Products cart updates...)
- Invalid or missing email security records (e.g. SPF, DKIM, DMARC)
- Session management issues (e.g. lack of expiration, no logout on password change, concurrent sessions)
- Disclosure of information without exploitable vulnerabilities and PoC (e.g. stack traces, path disclosure, directory listings, software versions, IP disclosure, 3rd party secrets, EXIF Metadata, Origin IP)
- CSV injection
- Malicious file upload (e.g. EICAR files, .EXE)
- HTTP Strict Transport Security Header (HSTS)
- Subdomain takeover without a full exploitable vulnerability and PoC or not applicable to the scope
- Blind SSRF without exploitable vulnerabilities and PoC (e.g. DNS & HTTP pingback, Wordpress XMLRPC)
- Lack or bypass of rate-limiting, brute-forcing or captcha issues
- User enumeration (e.g. email, alias, GUID, phone number, common CMS endpoints)
- Weak password policies (e.g. length, complexity, reuse)
- Ability to spam users (email / SMS / direct messages flooding)
- Disclosed or misconfigured public API keys (e.g. Google Maps, Firebase, analytics tools...)
- Password reset token sent via HTTP referer to external services (e.g. analytics / ads platforms)
- Stolen secrets, credentials or information gathered from a third-party asset that we have no control over
- Exposed secrets, credentials or information on an asset under our control that are not applicable to the program’s scope
- Pre-account takeover (e.g. account creation via oAuth)
- GraphQL Introspection is enabled
- Vulnerabilities requiring physical access to a user’s smartphone
- Exploits that are only possible on Android version 8 and below
- Exploits that are only possible on IOS version 14 and below
- Exploits that are only possible on a jailbroken device
- Exploiting a generic Android or iOS vulnerability
- Lack of code obfuscation
- Lack of binary protection / jailbreak and root detection / anti-debugging controls
- Crashing your own application
- Non important secrets (such as 3rd party secrets)
- SSL cypher suites
- Vulnerable version of libraries (for example ‘jquery’) without demonstrable attack vector SSL Pinning