Shutterfly VDP
By Shutterfly Vulnerability disclosure program on HackerOne shutterfly.com
- Top reward
- No cash rewards
- Top severity paid
- Critical
- Assets in scope
- 35
- 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 HackerOne
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 5 days
- As the policy promises.
- No public write-ups
- Keep findings private.
Rewards
What HackerOne lists as the payout for each severity.
This program does not pay cash rewards.
- Response
-
Within 5 days
| First Response | 5 days |
- Safe harbor
-
Full
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
35 assets you may test, 4 excluded.
Web 24
- admin.spoonflower.com Critical No bounty
- api-gateway.spoonflower.com Critical No bounty
- blog.spoonflower.com Critical No bounty
- cart.spoonflower.com Critical No bounty
- https://www.cvs.com/photo Critical No bounty
- jcpportraits.com Critical No bounty
- lifetouch.com Critical No bounty
- photo.walgreens.com Critical No bounty
- preschoolsmiles.com Critical No bounty
- prestigeportraits.com Critical No bounty
- shutterfly.com Critical No bounty
- shutterfly-prod.auth.us-east-1.amazoncognito.com Critical No bounty
- snapfish.com Critical No bounty
- snapfish.com.au Critical No bounty
- snapfish.co.nz Critical No bounty
- snapfish.co.uk Critical No bounty
- snapfish.de Critical No bounty
- snapfish.fr Critical No bounty
- snapfish.ie Critical No bounty
- snapfish.it Critical No bounty
- staging.spoonflower.com Critical No bounty
- tinyprints.com Critical No bounty
- wgwebservices.snapfish.com Critical No bounty
- www.spoonflower.com Critical No bounty
Wildcard domains 6
- *.lifetouch.com Critical No bounty
- *.photoccino.com Critical No bounty
- *.sbs.shutterfly.com Critical No bounty
- *.sf-cdn.com Critical No bounty
- *.shutterfly.com Critical No bounty
- *.snapfish.com Critical No bounty
iOS apps 3
- com.shutterfly.ShutterflyUploader Critical No bounty
- Snapfish: Photos Cards & Books / com.hp.Snapfish Critical No bounty
- Snapfish Photo Tile Wall Decor / com.snapfish-llc.SnapfishExpress Critical No bounty
Android apps 2
- com.shutterfly Critical No bounty
- Snapfish: Prints + Photo Books / com.snapfish.mobile Critical No bounty
Out of scope (4)
- fulfillment-platform.shutterfly.com
- www.borrowlenses.com
- *.cvs.com
- *.walgreens.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Shutterfly VDP (via HackerOne)'s policy. "We" in these lines means the program, not this site.
While testing
-
The Shutterfly program requires researchers to identify themselves by adding X-BugBounty: <username> where feasible.
-
Please provide detailed reports with reproducible steps.
-
Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
-
Social engineering (e.g. phishing, vishing, smishing) is prohibited.
-
Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
-
Only interact with accounts you own or with explicit permission of the account holder.
-
Automated testing must be rate-limited to avoid service degradation, and testing that exceeds reasonable request rates may be considered disruptive or out of scope.
-
You do not exfiltrate any data under any circumstances.
-
You do not conduct denial of service testing.
Not accepted
-
Attacks requiring MITM or physical access to a user's device.
-
Previously known vulnerable libraries without a working Proof of Concept.
-
Comma Separated Values (CSV) injection without demonstrating a vulnerability.
-
Any activity that could lead to the disruption of our service (DoS).
-
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
-
Rate limiting or brute force issues on non-authentication endpoints
-
Missing best practices in Content Security Policy.
-
Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
-
Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
-
Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
-
Issues that require unlikely user interaction
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, 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 added
www.borrowlenses.com (out of scope)
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 hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Shutterfly VDP looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.
Response Targets
Shutterfly VDP will make a best effort to meet the following SLAs for hackers participating in our program:
| Type of Response | SLA in business days |
|---|---|
| First Response | 5 days |
| Time to Triage | 10 days |
We’ll try to keep you informed about our progress throughout the process.
Disclosure Policy
- Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
- Follow HackerOne's disclosure guidelines.
Program Rules
- The Shutterfly program requires researchers to identify themselves by adding X-BugBounty: where feasible.
- Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged.
- Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
- When duplicates occur, we only triage the first report that was received (provided that it can be fully reproduced).
- Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.
- Social engineering (e.g. phishing, vishing, smishing) is prohibited.
- Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
- If it does not present a security vulnerability, any reports of suspected illicit content should be e-mailed to [email protected] and should not be submitted as reports to HackerOne.
Rate Limiting
Automated testing must be rate-limited to avoid service degradation, and testing that exceeds reasonable request rates may be considered disruptive or out of scope. Unless explicitly approved in advance, automated requests from a single researcher must not exceed the following limits:
- General pages: ≤ 30 requests per second
- API endpoints: ≤ 15 requests per second
- Authentication or other critical logic: ≤ 5 requests per second
#Asset in scope Any domain owned by Shutterfly Inc, listed in the Scope section will be eligible for submission.
Out of scope vulnerabilities
When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:
- Attacks requiring MITM or physical access to a user's device.
- Previously known vulnerable libraries without a working Proof of Concept.
- Comma Separated Values (CSV) injection without demonstrating a vulnerability.
- Any activity that could lead to the disruption of our service (DoS).
- Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
- Rate limiting or brute force issues on non-authentication endpoints
- Missing best practices in Content Security Policy.
- Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
- Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
- Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
- Issues that require unlikely user interaction
Safe Harbor
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
Thank you for helping keep Shutterfly and our users safe!
###Guidelines
Shutterfly will deal in good faith with researchers who discover, test, and submit vulnerabilities or indicators of vulnerabilities in accordance with these guidelines:
- Your activities are limited exclusively to:
- (1) Testing to detect a vulnerability or identify an indicator related to a vulnerability; or
- (2) Sharing with, or receiving from, Shutterfly information about a vulnerability or an indicator related to a vulnerability.
- You do no harm and do not exploit any vulnerability beyond the minimal amount of testing required to prove that a vulnerability exists or to identify an indicator related to a vulnerability.
- You avoid intentionally accessing the content of any communications, data, or information transiting or stored on Shutterfly information system(s) – except to the extent that the information is directly related to a vulnerability and the access is necessary to prove that the vulnerability exists.
- You do not exfiltrate any data under any circumstances.
- You do not intentionally compromise the privacy, confidentiality, or safety of Shutterfly personnel or any third parties.
- You do not intentionally compromise the intellectual property or other commercial or financial interests of any Shutterfly personnel or entities, or any third parties.
- You do not publicly disclose any details of the vulnerability, indicator of vulnerability, or the content of information rendered available by a vulnerability, except upon receiving explicit written authorization from Shutterfly.
- You do not conduct denial of service testing.
- You do not conduct social engineering, including spear phishing, of Shutterfly personnel or contractors.
- You submit any known or recommended remediations or mitigations with your report.