Report Security Issues

SECURITY VULNERABILITY REPORTING

If you’ve found a security vulnerability on marylebonediy.co.uk , we encourage you to contact us immediately. We will review all legitimate vulnerability reports and do our utmost to resolve the issue quickly. Before you report, please review this document, including the fundamentals, bounty program, reward guidelines, and what should not be reported.

Fundamentals

If you adhere to the principles below when reporting a security issue to Marylebone DIY, we will not initiate a lawsuit or enforcement investigation against you in response to your report.

We ask that:

  • You give us reasonable time to review and repair an issue you report before making public any information about the report or sharing such information with others.
  • You do not interact with a private account (which includes modifying or accessing data from the account) if the account owner has not consented to such actions.
  • You make an honest effort to avoid privacy violations and disruptions to others, including (but not limited to) destruction of data and interruption or degradation of our services.
  • You do not exploit a security issue you discover for any reason (this includes demonstrating additional risk, such as attempting to compromise sensitive company data or trying to find additional issues).
  • You do not violate other applicable laws or regulations.

BOUNTY PROGRAM

We recognize and reward security researchers who help us keep our platform safe by reporting vulnerabilities in our services. Monetary bounties for such reports are entirely at Marylebone DIY's discretion, supported by risk, impact, and other factors. To potentially qualify for a bounty, you must meet the following requirements:

  • Adhere to our fundamentals (see above).
  • Report a security bug: that is, identify a vulnerability in our services or infrastructure that creates a security or privacy risk. (Note that Marylebone DIY ultimately determines the risk of a problem, and many bugs may not be considered security issues.)
  • Submit your report via our security center. Please do not contact employees directly.
  • If you inadvertently cause a privacy violation or disruption (such as accessing account data, service configurations, or other confidential information) while investigating a vulnerability, inform us of this in your report.

We investigate and respond to all valid reports. Due to the number of reports we receive, we prioritize evaluations based on risk and other factors. It may take some time before you receive a reply.

We reserve the right to publish reports.

REWARDS

Our rewards are based on the impact of a vulnerability. We will update the program over time based on feedback, so please provide us with feedback on any areas of the program you think can be improved.

  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, it will not be eligible for a bounty.
  • When duplicates occur, we award the first report that we can fully reproduce.
  • Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
  • We determine the bounty reward based on a variety of factors, including (but not limited to) impact, ease of exploitation, and the quality of the report. We specifically note the bounty rewards, which are listed below.

The amounts listed below are the maximum we will pay per severity level. We aim to be fair, and all reward amounts are at our discretion.

  • Critical Severity Vulnerabilities (£200): Vulnerabilities that cause privilege escalation on the platform from unprivileged to admin, allow remote code execution, financial theft, etc.
    Examples:

    • Remote Code Execution
    • Remote Shell/Command Execution
    • Vertical Authentication Bypass
    • SQL Injection that leaks targeted data
    • Full account access

  • High Severity Vulnerabilities (£100): Vulnerabilities that affect the security of the platform, including the processes it supports.
    Examples:

    • Lateral Authentication Bypass
    • Disclosure of important information within the company
    • Cross-site Scripting (XSS) affecting another user
    • Local File Inclusion
    • Insecure handling of authentication cookies

  • Medium Severity Vulnerabilities (£50): Vulnerabilities that affect multiple users and require little or no user interaction to trigger.
    Examples:

    • Common logic design flaws and business process defects
    • Insecure Object References

  • Low Severity Vulnerabilities: Issues that affect individual users and require interaction or significant prerequisites (e.g., MITM) to trigger.
    Examples:

    • Open Redirect
    • Reflective XSS
    • Low Sensitivity Information Leaks