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 discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)

Introduction
We are happy to announce the Ivo.ai Vulnerability Disclosure Program.

Ivo.ai is looking for your help to identify security vulnerabilities across its approved web application, public APIs, Microsoft Word add-in, and authentication or authorization flows.

Researchers should focus on vulnerabilities that could affect user account security, document confidentiality, contract data, sensitive customer information, API security, authentication flows, authorization controls, or Ivo.ai-controlled functionality.

Only the assets listed in this program are in scope. Third-party services, corporate infrastructure, internal tooling, and systems not explicitly listed should not be tested unless Ivo.ai confirms otherwise.

Testing must remain controlled and non-disruptive. If researchers encounter sensitive user data, customer data, contract data, document content, internal Ivo.ai data, credentials, restricted functionality, or unintended access to another account or environment, testing must stop immediately and the issue should be reported with minimal evidence.

Worst-case scenarios

We are especially interested in vulnerabilities that could lead to:

• Unauthorized access to another user’s account
• Unauthorized access to customer documents, contracts, files, or document metadata
• Authentication bypass
• Authorization bypass
• Privilege escalation
• IDOR/BOLA affecting users, documents, contracts, organisations, or API resources
• Session or token compromise
• Sensitive data exposure
• Access to internal Ivo.ai data or restricted functionality
• API vulnerabilities exposing user, customer, document, or account data
• Microsoft Word add-in vulnerabilities affecting document confidentiality or integrity
• Cross-tenant or cross-organisation access
• Remote code execution on Ivo.ai-controlled systems
• SQL injection, SSRF, command injection, path traversal, or other injection vulnerabilities with practical impact
• Stored or reflected XSS with demonstrated user or account impact
• Business logic flaws affecting document workflows, account access, authentication, authorization, or customer data

Useful infrastructure information

The approved scope includes:

• The Ivo web application: https://app.ivo.ai
• Ivo public APIs
• The Ivo Microsoft Word add-in
• Authentication and authorization flows

Researchers should not test third-party services or integrations that Ivo.ai does not control.

Corporate infrastructure, email systems, identity provider admin consoles, internal tooling, and services not exposed to the public internet are not in scope unless explicitly approved by Ivo.ai.

Application

• 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.
• Best practices violations (password complexity, expiration, re-use, etc.)
• 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
• Content injection without being able to modify the HTML
• Username/email enumeration
• Email bombing
• HTTP Request smuggling without any proven impact
• Homograph attacks
• XMLRPC enabled
• Banner grabbing/Version disclosure
• 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 are usually not eligible for a bounty
• Reports that state that software is out of date/vulnerable without a proof-of-concept

This program follows Intigriti's triage standards based on the proof of concept.

Where can we get credentials for the app?

We currently don’t offer any credentials to test user roles.