Vulnerability disclosure program

Thank you for your interest in the vulnerability disclosure program. We have implemented this program to encourage the identification and reporting of security vulnerabilities to ensure the continued security of our platform and services. Please thoroughly review the program terms before you test or report a vulnerability.

Writer reserves the right to modify the terms of this policy at any time.

Response targets

When you submit a report, Writer will make reasonable effort to meet the following targets:

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.

Scope leniency

This program will not accept submissions for assets that are not listed as in scope.

Program rules

• 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 the explicit permission of the account holder.

In-scope assets

• app.writer.com
• api.writer.com
• Chrome Browser Extension
• Edge Browser Extension
• Contentful Plugin
• Word Plugin
• Figma Plugin
• Outlook Plugin
• Mac OS Desktop Application
• Windows Desktop Application

Out-of-scope assets

• writer.com and www.writer.com
• WordPress domains and configurations

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:

• Clickjacking on pages with no sensitive actions
• Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
• Content spoofing on pages with no sensitive actions
• 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
• Missing best practices in SSL/TLS configuration
• Any activity that could lead to the disruption of our service (DoS)
• Rate-limiting or brute force issues on non-authentication endpoints
• Missing best practices in Content Security Policy (CSP)
• Missing best practices in DNS Configuration
• Missing HttpOnly or Secure flags on cookies
• Configuration of or missing security headers
• Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
• Vulnerabilities only affecting users of outdated or unpatched browsers (More 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)
• Tabnabbing
• User Enumeration
• Issues that require unlikely user interaction
• Improper logout functionality and improper session timeout
• CORS misconfiguration without an exploitation scenario
• Broken link hijacking
• Lack of SSL Pinning
• Password length, complexity, and re-use requirements
• Vulnerabilities on third-party websites
• Physical attacks on Writer personnel, property, or data centers or other vulnerabilities requiring physical proximity
• Obtaining data not in the control of the application
• Reports from automated tools or scanners
• Vulnerabilities on the Writer marketing website writer.com and www.writer.com

Thank you for helping keep Writer and our users safe!