- Top reward
- No cash rewards
- Top severity paid
- Critical
- 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 on HackerOne
- Submit through the program page.
- Partial safe harbor
- Some legal protection; read the terms.
- No public write-ups
- Keep findings private.
Rewards
What HackerOne lists as the payout for each severity.
This program does not pay cash rewards.
- Safe harbor
-
Partial
By following these guidelines and responsibly disclosing any security weaknesses solely and directly to Taxwell, we agree not to pursue legal action against you. Taxwell reserves its legal rights in the event of noncompliance with program guidelines.
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
6 assets you may test, 1 excluded.
Web 6
- 1040.com Critical No bounty
- drakesoftware.com Critical No bounty
- securefilepro.com Critical No bounty
- taxact.com Critical No bounty
- taxwell.com Critical No bounty
- taxwell.org Critical No bounty
Out of scope (1)
- taxactonline.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Taxwell VDP (via HackerOne)'s policy. "We" in these lines means the program, not this site.
While testing
-
Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
-
Understand when duplicates occur, we only recognize the first report that was received; provided, it can be fully reproduced.
-
Combine into a single report, multiple vulnerabilities caused by one underlying issue.
-
Make a good faith effort to avoid privacy violations, data destruction, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
-
Provide a clear, concise description of the steps needed to reproduce any vulnerability you submit.
-
Provide the complete details related to the security issue, including proof-of-concept (POC) URL, as well as the details of the system(s) where tests have been conducted.
-
Cause harm to Taxwell, its customers, shareholders, partners, or employees.
-
Engage in any act that may cause an outage or negatively impact any Taxwell service.
-
Engage in illegal activities or any acts that violate any law, rule, or regulation.
-
Store, share, compromise, or destroy any Taxwell or customer data. If personally identifiable information is encountered, you are required to stop and immediately notify Taxwell.
Not accepted
-
Phishing
-
Social engineering
-
Physical security assessments
-
Any form of denial of service (DoS) attack
-
Clickjacking on pages with no sensitive actions
-
Authentication logic, flows and control mechanisms
-
Cross-Site Request Forgery on unauthenticated forms or forms with no sensitive actions
-
Attacks requiring MITM or physical access to a user's device
-
Previously known vulnerable libraries without a working POC
-
Comma Separated Values injection without demonstrating a vulnerability
-
Missing best practices in SSL/TLS configuration
-
Any activity by a security researcher that could lead to the disruption of our service
-
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
-
Rate limiting or bruteforce issues (we use various solutions to monitor and respond to anomalous traffic)
-
Missing best practices in Content Security Policy
-
Missing HttpOnly or Secure flags on cookies
-
Missing email best practices (invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
-
Vulnerabilities only affecting users of outdated or unpatched browsers, i.e., 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)
-
Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be recognized on a case-by-case basis
-
Tabnabbing
-
Open redirect - unless an additional security impact can be demonstrated
-
Issues that require unlikely user interaction
-
Sessions not invalidated or devices not unlinked after password change
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 1 hour 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.
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.
Program Policy
Security researchers will disclose potential weaknesses in compliance with the following guidelines: Do
- Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
- Understand when duplicates occur, we only recognize the first report that was received; provided, it can be fully reproduced.
- Combine into a single report, multiple vulnerabilities caused by one underlying issue.
- Make a good faith effort to avoid privacy violations, data destruction, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
- Provide a clear, concise description of the steps needed to reproduce any vulnerability you submit.
- Provide the complete details related to the security issue, including proof-of-concept (POC) URL, as well as the details of the system(s) where tests have been conducted.
Don't
- Cause harm to Taxwell, its customers, shareholders, partners, or employees.
- Engage in any act that may cause an outage or negatively impact any Taxwell service.
- Engage in illegal activities or any acts that violate any law, rule, or regulation.
- Store, share, compromise, or destroy any Taxwell or customer data. If personally identifiable information is encountered, you are required to stop and immediately notify Taxwell.
- Conduct fraudulent activity or complete fraudulent financial transactions.
Disclosure Policy
- Taxwell does not allow disclosure. Please do not discuss any vulnerabilities (even resolved ones) outside of the program without express written consent from Taxwell.
- Follow HackerOne's disclosure guidelines. However, if any provision of those guidelines conflict with the preceding bullet point, the preceding bullet point shall control.
Test Plan
- When creating an account for testing, please use the following syntax for email: [email protected], or use your @wearehackerone.com alias.
- When researching for a vulnerability, only use accounts you own. Do not attempt to use another user's account.
To help accelerate our validation of reports, please tag your traffic and include identifiers in your reports. Some examples include:
| Header | Value |
|---|---|
| X-Bug-Bounty: | HackerOne- |
| X-HackerOne: | |
| User-Agent: | / <H1: username> |
Out of scope vulnerabilities
When reporting vulnerabilities, please consider the attack scenario, exploitability, and security impact of the bug. The following types of vulnerabilities are out of scope for this program:
- Phishing
- Social engineering
- Physical security assessments
- Any form of denial of service (DoS) attack
The following issues are considered out of scope:
- Clickjacking on pages with no sensitive actions
- Authentication logic, flows and control mechanisms
- Cross-Site Request Forgery on unauthenticated forms or forms with no sensitive actions
- Attacks requiring MITM or physical access to a user's device
- Previously known vulnerable libraries without a working POC
- Comma Separated Values injection without demonstrating a vulnerability
- Missing best practices in SSL/TLS configuration
- Any activity by a security researcher that could lead to the disruption of our service
- Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
- Rate limiting or bruteforce issues (we use various solutions to monitor and respond to anomalous traffic)
- Missing best practices in Content Security Policy
- Missing HttpOnly or Secure flags on cookies
- Missing email best practices (invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
- Vulnerabilities only affecting users of outdated or unpatched browsers, i.e., 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)
- Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be recognized on a case-by-case basis
- Tabnabbing
- Open redirect - unless an additional security impact can be demonstrated
- Issues that require unlikely user interaction
- Sessions not invalidated or devices not unlinked after password change
- **Copy/paste tool output (e.g., WPScan results, SSL Labs links) as a report. ** A POC and detailed description on how it can affect a user's data, or Taxwell data/infrastructure must be included to be a valid finding and will be recognized on a case-by-case basis
- Pursuing vulnerabilities which send unsolicited bulk messages (spam) or unauthorized messages
- Arbitrary File Download
- TaxAct Mobile App
Please note:
- Any testing that has a negative impact on the availability of our products and services can result in being blocked or banned.
Submission Guidelines
All potential weaknesses submitted must include sufficient information to reproduce and validate the issue. Documentation should include a detailed summary of the issue, target(s), steps performed, screenshots, tools utilized, and any information that will help Taxwell during triage. By following these guidelines and responsibly disclosing any security weaknesses solely and directly to Taxwell, we agree not to pursue legal action against you. Taxwell reserves its legal rights in the event of noncompliance with program guidelines.
Privacy and Security Notice
Taxwell is committed to leveraging technology in a way that provides you transparency on how we collect, process, and share personal information, as described in the privacy notices set forth on the applicable websites for our products and services. TaxAct Privacy Notice and Drake Software Privacy Notice