Skip to content

Bentley Systems

Bug bounty on Self-hosted bentley.com

Accepting reports Full safe harbor KYC to get paid
Top reward
$1,200
Top severity paid
Not published
Assets in scope
14
Public CVEs
60
Last change
No changes yet

At a glance

What to know before you start testing.

Pays up to $1,200
top reward, from $100.
Full safe harbor
Good-faith research is authorised; no legal action.
Paid by PayPal
Proof of identity needed to get paid.
Publish after a fix
Coordinate the timing with the company.

Rewards

What the company's own policy page says it pays.

The policy page has no reward table. Here is what it says, in its own words.

Top reward
$1,200 Remote Code Execution │ 1200
Lowest reward
$100 DLL hijacking │ 100
Safe harbor
Full Not to pursue or support any legal action related to your research.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

14 assets you may test, 12 excluded.

Domains 8

  • bentley.com
  • community.seequent.com
  • eventhub.bentley.com
  • events.seequent.com
  • imodeljs.org
  • lms.seequentlearning.com
  • partners.seequent.com
  • seequent.frontify.com

Desktop and binaries 1

  • All Bentley Systems desktop products (Only CONNECT Edition and Later)

Source code 1

  • All Bentley Open-Source Projects (including imodeljs.org)

Wildcard domains 1

  • all _.bentley.com subdomains

Products and areas 3

  • All Bentley Cloud Applications and Services
  • All Bentley Systems mobile apps (distributed only on Play and App stores)
  • Bentley Systems’ Infrastructure (VPN, Mail Server, SharePoint, Skype, etc.)
Out of scope (12)
  • eventhub.bentley.com
  • Any services hosted by 3rd-party providers and services
  • Findings derived primarily from social engineering (e.g., phishing, vishing)
  • Findings from applications or systems not listed in the ‘Scope’ section
  • Findings from physical testing, such as office access (e.g., open doors, tailgating)
  • Obsolete/deprecated software
  • On24 related issues
  • https://community.seequent.com
  • https://events.seequent.com
  • https://lms.seequentlearning.com
  • https://partners.seequent.com
  • https://seequent.frontify.com

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Bentley Systems's policy. "We" in these lines means the program, not this site.

While testing

  • Avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security testing.
  • Perform research only within the scope set out below.
  • Keep information about any vulnerabilities you have discovered confidential between you and Bentley Systems until it is fixed.
  • DoS is strictly prohibited.
  • Any form of credentials brute forcing is strictly prohibited.
  • Public disclosure of a reported vulnerability before it has been fixed is prohibited.
  • You may not destroy or degrade our performance or violate the privacy or integrity of our users and their data.
  • Exploiting vulnerabilities (other than a generic PoC) is strictly prohibited and will be prosecuted according to applicable law.
  • Limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept; and

Not accepted

  • DoS, and application-level DoS (unless the response is asymmetrical compared to the initial request)
  • Publicly released bugs in internet software within 15 days of their disclosure
  • Self-XSS (we require evidence on how the XSS can be used to attack another user)
  • CSRF without any security impact (e.g. Logout CSRF)
  • X-Frame-Options related (clickjacking)
  • Header injection (unless you can show how they can lead to stealing user data)
  • Issues that are non-exploitable but lead to crashes, stack trace, and similar information leak or stability issues.
  • Version exposure (unless you deliver a PoC of working exploit).
  • Anything requiring outdated browsers, platforms, or crypto (i.e. TLS BEAST, POODLE, etc.)
  • Spam or Social Engineering techniques, including SPF and DKIM issues
  • Rate limit vulnerability not on a login functionality (unless a valid exploit PoC provided)
  • XMLRPC.php file is enabled leading to DoS attack
  • Missing cookie flags on non-sensitive cookies
  • Missing security headers which do not lead directly to a vulnerability (unless you deliver a PoC)
  • Anything from an automated scan
  • Anything that is public by default (e.g. public keys, config files without sensitive information, etc.)
  • Anything not under Bentley Systems control (e.g. Google Analytics, etc.)
  • Theoretical issues that lack practical severity
  • UI and UX bugs and spelling mistakes
  • Credentials found at breach forums like [https://breachforums.st, https://phonebook.cz] etc.
  • CAA certificate missing
  • User enumeration in WP, when only a few Bentley employees, who posted on the website, are exposed
  • Origin IP exposure
  • Misconfigurations on non-resolving URLs
  • AppInsights key exposure

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 5 hours 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.

Search NVD
CVESeverityPublished
CVE-2022-43656 Medium 5.5 7 May 2024
CVE-2022-43651 High 7.8 7 May 2024
CVE-2022-43652 Medium 5.5 7 May 2024
CVE-2022-43653 High 7.8 7 May 2024
CVE-2022-43655 High 7.8 7 May 2024
CVE-2023-44430 High 7.8 3 May 2024
CVE-2023-51708 High 8.6 22 Dec 2023
CVE-2023-4863 High 8.8 12 Sep 2023
CVE-2022-28641 High 7.8 29 Mar 2023
CVE-2022-28642 High 7.8 29 Mar 2023
CVE-2022-28643 High 7.8 29 Mar 2023
CVE-2022-28644 High 7.8 29 Mar 2023
CVE-2022-28645 Medium 5.5 29 Mar 2023
CVE-2022-28646 High 7.8 29 Mar 2023
CVE-2022-28647 High 7.8 29 Mar 2023
CVE-2022-28306 High 7.8 29 Mar 2023
CVE-2022-28307 High 7.8 29 Mar 2023
CVE-2022-28308 Medium 5.5 29 Mar 2023
CVE-2022-28309 Medium 5.5 29 Mar 2023
CVE-2022-28310 High 7.8 29 Mar 2023
CVE-2022-28311 High 7.8 29 Mar 2023
CVE-2022-28312 Medium 5.5 29 Mar 2023
CVE-2022-28313 Medium 5.5 29 Mar 2023
CVE-2022-28314 High 7.8 29 Mar 2023
CVE-2022-28315 High 7.8 29 Mar 2023
CVE-2022-28316 High 7.8 29 Mar 2023
CVE-2022-28317 High 7.8 29 Mar 2023
CVE-2022-28318 High 7.8 29 Mar 2023
CVE-2022-28319 High 7.8 29 Mar 2023
CVE-2022-28320 High 7.8 29 Mar 2023
CVE-2022-28300 High 7.8 29 Mar 2023
CVE-2022-28301 High 7.8 29 Mar 2023
CVE-2022-28302 High 7.8 29 Mar 2023
CVE-2022-28303 High 7.8 29 Mar 2023
CVE-2022-28304 High 7.8 29 Mar 2023
CVE-2022-28305 High 7.8 29 Mar 2023
CVE-2022-1229 High 7.8 28 Mar 2023
CVE-2022-40201 High 7.8 6 Jan 2023
CVE-2022-41613 High 7.8 6 Jan 2023
CVE-2022-42899 High 7.8 13 Oct 2022
CVE-2022-42900 High 7.8 13 Oct 2022
CVE-2022-42901 High 7.8 13 Oct 2022
CVE-2022-35904 Low 3.3 15 Jul 2022
CVE-2022-35905 Low 3.3 15 Jul 2022
CVE-2022-35906 Low 3.3 15 Jul 2022
CVE-2022-35900 Low 3.3 15 Jul 2022
CVE-2022-35901 Low 3.3 15 Jul 2022
CVE-2022-35902 Low 3.3 15 Jul 2022
CVE-2022-35903 Low 3.3 15 Jul 2022
CVE-2021-46646 High 7.8 18 Feb 2022
CVE-2021-46647 High 7.8 18 Feb 2022
CVE-2021-46648 High 7.8 18 Feb 2022
CVE-2021-46649 Medium 5.5 18 Feb 2022
CVE-2021-46650 Medium 5.5 18 Feb 2022
CVE-2021-46651 Medium 5.5 18 Feb 2022
CVE-2021-46652 High 7.8 18 Feb 2022
CVE-2021-46653 High 7.8 18 Feb 2022
CVE-2021-46654 Medium 5.5 18 Feb 2022
CVE-2021-46655 High 7.8 18 Feb 2022
CVE-2021-46656 High 7.8 18 Feb 2022