- Top reward
- €2,000
- Top severity paid
- Critical
- Assets in scope
- 43
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- Pays up to €2,000
- for critical bugs, from €100.
- 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.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
€2,000 from €1,000 |
| High |
|
€500 |
| Medium |
|
€200 |
| Low |
|
€100 |
Scope
43 assets you may test, 2 excluded.
Web 41
- api.posti.fi
- auth-service.posti.fi
- cdn.posti.fi
- connect.posti.fi
- console.posti.com
- developer.posti.com
- elma.elma.fi
- gateway.posti.fi
- https://kontakti.posti.fi
- https://my.account.posti.fi
- https://my.smartposti.ee
- https://my.smartposti.lt
- https://my.smartposti.lv
- https://oma.posti.fi
- https://printerdriver.posti.com
- https://pro.posti.fi
- https://quicksight.aws.amazon.com
- https://shop.posti.fi
- https://tuleasiakkaaksi.posti.fi
- https://www.posti.fi
- https://www.smartposti.ee
- https://www.smartposti.lt
- https://www.smartposti.lv
- https://www.webproteus.com/lpro-web/login
- https://yrityksennoutopiste.posti.fi
- id.posti.fi
- jakelu.posti.fi
- logout.id.posti.fi
- mfa.posti.fi
- netposti.fi
- nextshipping.posti.fi
- orgadmin-ext.prd.account.posticloud.fi
- partnerselfservice.posti.fi
- picc.posti.fi
- posti.com
- postikuori.posti.fi
- tnt.posti.com
- todentaminen.posti.fi
- www.posti.se
- yhteystietoni.posti.fi
- yritysmuutto.posti.fi
Android apps 1
- fi.itella.posti.android
iOS apps 1
- 410789057
Out of scope (2)
- https://developer.posti.com/support-request
- www.posti.fi/henkiloasiakkaat/lomakkeet/tuotantohairiot.html
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Posti Bug Bounty (via Intigriti)'s policy.
While testing
-
Respect the scope of the program
-
Not to discuss or disclose vulnerability information with any third parties in any form and at any time
-
it's not allowed to proceed to a legitimate purchase
-
No systems should be intentionally disrupted.
-
they should not continue to the actual step that would bring down the system
-
please use your @intigriti.me address
-
your account / profile should not include fake data
-
Do not send actual support requests via this form.
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
-
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
-
Weak SSL/TLS ciphers without a demonstrable exploit
-
Content injection without being able to modify the HTML
-
Username/email enumeration
-
Employee emails disclosure
-
Email bombing
-
HTTP Request smuggling without any proven impact
-
Homograph attacks
-
XMLRPC enabled
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 30 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://developer.posti.com/support-request (out of scope)
-
Scope removed
gateway.posti.fi
-
Scope removed
mfa.posti.fi
-
Scope removed
yhteystietoni.posti.fi
-
Scope removed
fi.itella.posti.android
-
Scope removed
https://printerdriver.posti.com/
-
Scope removed
yritysmuutto.posti.fi
-
Scope removed
https://www.posti.fi
-
Scope removed
console.posti.com
-
Scope removed
https://www.smartposti.lt
-
Scope removed
https://oma.posti.fi/
-
Scope removed
https://shop.posti.fi
-
Scope removed
postikuori.posti.fi
-
Scope removed
todentaminen.posti.fi
-
Scope removed
https://yrityksennoutopiste.posti.fi
-
Scope removed
partnerselfservice.posti.fi
-
Scope removed
https://tuleasiakkaaksi.posti.fi
-
Scope removed
https://my.smartposti.lv
-
Scope removed
auth-service.posti.fi
-
Scope removed
https://my.smartposti.ee/
-
Scope removed
logout.id.posti.fi
-
Scope removed
elma.elma.fi
-
Scope removed
https://quicksight.aws.amazon.com
-
Scope removed
picc.posti.fi
-
Scope removed
tnt.posti.com
-
Scope removed
https://my.account.posti.fi
-
Scope removed
www.posti.fi/henkiloasiakkaat/lomakkeet/tuotantohairiot.html (out of scope)
-
Scope removed
netposti.fi
-
Scope removed
https://www.smartposti.lv
-
Scope removed
https://my.smartposti.lt
-
Scope removed
410789057
-
Scope removed
https://kontakti.posti.fi
-
Scope removed
api.posti.fi
-
Scope removed
https://pro.posti.fi
-
Scope removed
www.posti.se
-
Scope removed
nextshipping.posti.fi
-
Scope removed
posti.com
-
Scope removed
https://www.smartposti.ee
-
Scope removed
connect.posti.fi
-
Scope removed
https://www.webproteus.com/lpro-web/login
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 Posti bug bounty programme!
Posti is one of the leading delivery and fulfillment companies in Finland, Sweden and the Baltic countries, that offers a wide range of postal, logistics, freight and eCommerce services.
Thank you for your interest in helping us protect our products, services and users. We appreciate the time, effort and competence that you offer to make our company more secure. Thank you in advance for your valuable contributions.
Before reporting, please read very carefully the scope of the programme, the rules of engagement and the out of scope section.
When reporting, please provide well structured submissions with clear and logical reproduction steps, the affected endpoints and the minimal evidence needed to demonstrate the impact of the issue. The clearer and more understandable a report is, the sooner we will get back to you. Please do not mention any theoretical, hypothetical scenarios but only concretely exploitable cases.
We will do our best, considering our teams workload, schedules and availability, to promptly acknowledge the submissions, investigate the issues and keep you informed.
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 to discuss or disclose vulnerability information with any third parties in any form and at any time
Important
-
When testing webshops where it's possible to order and/or buy Posti products and services (such as stamps, parcels, etc.) it can be tested for example if it's possible to buy them without actually paying for them but it's not allowed to proceed to a legitimate purchase. Posti will not refund any possible costs that the security researchers might incur when trying to purchase any products and services.
-
No systems should be intentionally disrupted. The security researchers can demonstrate that by taking some steps, a system might potentially be disrupted but they should not continue to the actual step that would bring down the system.
In scope
Introduction We have done our best to build secure systems and now we would like to ask for your help to spot something that we might have missed.
The focus areas of the programme are outlined in the assets list. As follows a few examples of cases where we are particularly interested:
- An attacker manages to modify data in Posti systems
- An attacker gains access to our customers personal data
- An attacker manages to bring down our systems making them inaccessible
- Ransomware attacks
Test accounts and credentials No accounts and credentials will be provided by Posti. If they want, the researchers with Finnish bank credentials or IDs, can create their own real account in those systems which allow it (please notice, only real account data must be provided). If you cannot create an account by yourself, that's ok.
Feedback Would you like to help us improve our program or have some feedback to share (for example, would you like to suggest adding to the program an API or a domain related to those already in the scope)? Then 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
Known Issues (last updated: 11 November 2026)
POSTI-Z3C1M22X, POSTI-M3HSS4E8 - shop.posti.fi//api/cart/
Do not report issues related to the missing authorization check on the cart API (unless you can demonstrate how to obtain other users valid cartIDs).
POSTI-3W3YADF0 - my.smartposti.ee - my.smartposti.lv - my.smartposti.lt /api/safe_place_note/
Please do not report issues regarding the /api/safe_place_note/ endpoint allowing creating notes and/or attachments on behalf of other users.
POSTI-78U1JCCK - tnt.posti.com/Portal/Reporting/definitions/reportingPipelineUnsubscribe
The endpoint performs the unsubscribe action without requiring any authentication. Do not report attacks unsubscribing arbitrary e-mail address from the report pipelines.
POSTI-MUWK32N1, POSTI-8BMQS3IV - [www.posti.fi, graphql.posti.fi, oma.posti.fi]
Please notice that the consumerShipment resolver accepts tokens issued to anonymous users, which means that public tracking is a feature that Posti provides. Therefore please do not report anonymous / unauthenticated shipment data exposure involving the consumerShipment resolver. The information that can be exposed includes:
- Shipment tracking numbers
- Internal shipment IDs
- Shipment types
- Transport status
- Destination postal codes
- Destination cities
POSTI-0SL6UQL8 - https://www.netposti.fi/public-ws/messageContent.pdf?msg=
After logging in to the oma.posti.fi service, the endpoint https://www.netposti.fi/public-ws/messageContent.pdf?msg= allows access to documents by simply accessing the URL with the msg parameter. Do not report such issue.
https://developer.posti.com/support-request
Do not send actual support requests via this form. Such requests unnecessarily create real support tickets.
POSTI-M2R4VUYA - [shop.posti.fi] - Business Logic: VAT calculation
Do not report any issues regarding the VAT calculation.
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
- Information disclosure of non-sensitive data (version disclosure, banner grabbing or other banner identification issues, descriptive error messages or headers, stack traces, application or server errors) without a direct and demonstrated exploit
- 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
- Missing security best practices or best practices violations that do not pose a direct security risk or a demonstrated exploit
- 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
- Weak SSL/TLS ciphers without a demonstrable exploit
- Content injection without being able to modify the HTML
- Username/email enumeration
- Employee emails disclosure
- Email bombing
- HTTP Request smuggling without any proven impact
- Homograph attacks
- XMLRPC enabled
- 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 they are not eligible for a bounty unless a direct and case-specific exploit is demonstrated
- 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?
We don’t provide any credentials to test user roles. However, if the application offers a self-register functionality, you can create your personal account. If you decide to do so, please use your @intigriti.me address and keep in mind that the domains in the scope of the program are mostly production environments, therefore your account / profile should not include fake data.