Reward

BountyHall of fame

€50 Low €100 Medium €500 High €1,000 Critical €3,000

Program

Avg reward €472.03

Max reward €3,000

Scopes20

Supported languagesEnglish

Hacktivity

Reports460

1st response < 1 day

Reports last 24h2

Reports last week6

Reports this month19

Program description

Program activity

About

VINCI

VINCI is a world leader in concessions, energy and construction sector.

Security is very important to us, this Bug Bounty program shall help us ensure the good level of security of our external assets (VINCI Holding scope).

VINCI's public Bug Bounty program

This program concerns our main public web sites, including some applications allowing user enrollment (grey box testing).

Program Rules

Testing Policy and Responsible Disclosure

Please adhere to the following rules while performing research on this program:

Use the User Agent mentionned below to hunt on this bug bounty program !
Denial of service (DoS) attacks on VINCI applications, servers, networks or infrastructure are strictly forbidden.
Avoid tests that could cause degradation or interruption of our services.
Do not use automated scanners or tools that generate large amount of network traffic.
Do not leak, manipulate, or destroy any user data or files in any of our applications/servers.
Do not copy any files from our applications/servers and disclose them.
No vulnerability disclosure, full, partial or otherwise, is allowed.

Reward Eligibility

We are happy to thank everyone who submits valid reports which help us improve our security, however only those that meet the following eligibility requirements may receive a monetary reward:

You must be the first reporter of a vulnerability.
The vulnerability must be a qualifying vulnerability (see below).
The report must contain the following elements:
Clear textual description of the vulnerability, how it can be exploited, the security impact it has on the application, its users and our organisation, and remediation advice on fixing the vulnerability
Proof of exploitation: screenshots demonstrating the exploit was performed, and showing the final impact
Provide complete steps with the necessary information to reproduce the exploit, including (if necessary) code snippets, payloads, commands etc
You must not break any of the testing policy rules listed above.
You must not be a former or current employee of our organisation or one of its contractors.
If you find the same vulnerability several times, please create only one report and eventually use comments. You'll be rewarded according to your findings.
The triage team will use the "One Fix One Reward" process: if two or more endpoints/forms use the same code base and a single fix can be deployed to fix all the other weaknesses, only one endpoint will be considered as eligible for a reward and other reports will be closed as Informative/Duplicate.

Reward amounts are based on:

Reward grid of the report's scope
CVSS scoring and actual business impact of the vulnerability upon performing risk analysis

Additional provision and testing conditions

Regarding accounts

No accounts will be provided in the framework of this program but you're welcome nonetheless to self-register whenever possible on our applications.

If you do self-register, please use your YesWeHack aliases to create your accounts as it will help us triage your report more easily and greatly speed up the process. You can retrieve your aliases https://yeswehack.com/user/my-yeswehack/email-alias.

Regarding Forms and contact/reservation features

Please use your YWH aliases (*@yeswehack.ninja) whenever testing forms or contact features and, if possible, append the following message to free input fields (e.g. message body or comment) :

[Bug Bounty, please ignore - Contact VINCI Cybersecurity audit if needed]

It'll help us triage your reports more seamlessly.

Regarding shared code base and framework

Please note that some of our scopes may share the same framework/code base which means that any given vulnerability might be found on several scopes but is likely to necessitate only one fix on our end. In such a case your findings might be considered as duplicates and thus won't be eligible for reward.

Nonetheless, you're more than welcome to check if your findings apply to other scopes and if they do not share the same root cause/necessitate several fixes on our side you'll be rewarded accordingly.

Regarding third parties solutions

Some of our assets are based on third parties solution even though specific developments were undertaken.

Thus, for such applications, we're interested in any vulnerability pertaining to configuration/settings issues or to our proprietary code but mind that vulnerabilities related to our providers' platforms/solutions/modules might not be eligible for rewards as it's not under our management nor responsibility.

Reports of leaks and exposed credentials

In the context of this program, we do not intend to encourage, accept or reward reports of leaks or exposed credentials.

We will only consider vulnerabilities or leaks that are identified directly on the scope of this program.

Also, in order not to encourage dark and grey economies, in particular the purchase, resale and trade of identifiers or stolen information, as well as all types of dangerous behaviour (e.g. social engineering, ...), we will not accept or reward any report based on information whose source is not the result of failure on the part of our organization or one of our employees/service providers.

This excludes, but is not limited to:

Stolen credentials gathered from unidentified sources
Exposed credentials on an out-of-scope assets
Exposed GitHub/GitLab (or similar) instance
Exposed secrets (e.g. API tokens/keys or other technical credentials)
Exposed PII on an out-of-scope asset

To summarize our policy, you may refer to this table :

| Source of leak is in-scope | Source of leak is out-of-scope |

Impact is in-scope (e.g. valid credentials on an in-scope asset) | Eligible | Not Eligible |

Impact is out-of-scope (e.g. valid credentials for an out-of-scope asset) | Eligible | Not Eligible |

Impacted asset must be under VINCI SA's responsability.

Reward

Asset value | CVSS Low | CVSS Medium | CVSS High | CVSS Critical | High | €100 | €500 | €1,000 | €3,000 | Medium | €100 | €400 | €800 | €2,000 | Low | €50 | €300 | €600 | €1,500 |

Scopes

Medium €500

High €1,000

Critical €3,000

Medium €400

High €800

Critical €2,000

Medium €400

High €800

Critical €2,000

| survey.vinci.com | Web application | Low | | Low €50

Medium €300

High €600

Critical €1,500

Medium €400

High €800

Critical €2,000

Medium €400

High €800

Critical €2,000

| vœux.vinci.com | Web application | Low | | Low €50

Medium €300

High €600

Critical €1,500

Medium €400

High €800

Critical €2,000

Medium €400

High €800

Critical €2,000

Medium €500

High €1,000

Critical €3,000

Medium €400

High €800

Critical €2,000

Medium €400

High €800

Critical €2,000

Medium €400

High €800

Critical €2,000

Medium €400

High €800

Critical €2,000

| solutions-environnement.vinci.com | Web application | Low | | Low €50

Medium €300

High €600

Critical €1,500

| essentiel.vinci.com | Web application | Low | | Low €50

Medium €300

High €600

Critical €1,500

| essentials.vinci.com | Web application | Low | | Low €50

Medium €300

High €600

Critical €1,500

| www.chaire-arpenter.fr | Web application | Low | | Low €50

Medium €300

High €600

Critical €1,500

Medium €400

High €800

Critical €2,000

Medium €400

High €800

Critical €2,000

Out of scopes

Please note that www.lafabriquedelacite.com is out of scope from today 10/12/25 as the web site is going to be redeveloped.
Anything that is not explicitely listed in scope section
!! Links pointing to other FQDNs are always out of scope !!
only exception: wishes.vinci.com (english version of voeux.vinci.com) is included in the scope
All PDF documents published or served on castor.vinci.com are public, thank you for not reporting any bug linked to the accessibility of these documents.

Vulnerability types

Qualifying vulnerabilities

SQL Injection (SQLi)
Cross-Site Scripting (XSS) with real security impact
Remote Code Execution (RCE)
Insecure Direct Object Reference (IDOR) with real security impact
Horizontal and vertical privilege escalation
Authentication bypass & broken authentication
Business Logic Errors vulnerability with real security impact
Local files access and manipulation (LFI, RFI, XXE, SSRF, XSPA)
Cross-Origin Resource Sharing (CORS) with real security impact
Cross-site Request Forgery (CSRF) with real security impact
Open Redirect with real security impact
Exposed secrets, credentials or sensitive information from an in-scope asset

Non-qualifying vulnerabilities

Broken Link/Social media Hijacking
Tabnabbing
Missing cookie flags
Content/Text injections
Mixed content warnings
Clickjacking/UI redressing
Denial of Service (DoS) attacks, including cache poisoning
Known CVEs without working PoC
Open ports without real security impact
Social engineering of staff or contractors
Presence of autocomplete attribute on web forms
Vulnerabilities affecting outdated browsers or platforms
Self-XSS or XSS that cannot be used to impact other users
Outdated libraries without a demonstrated security impact
Any hypothetical flaw or best practices without exploitable PoC
Expired certificate, best practices and other related issues for TLS/SSL certificates
Unexploitable vulnerabilities (ex: XSS or Open Redirect in HTTP Host Header)
Reports with attack scenarios requiring MITM or physical access to victim's device
Missing security-related HTTP headers which do not lead directly to a vulnerability
Unauthenticated / Logout / Login and other low-severity Cross-Site Request Forgery (CSRF)
Invalid or missing SPF (Sender Policy Framework), DKIM, DMARC records
Session expiration policies (no automatic logout, invalidation after a certain time or after a password change)
Disclosure of information without direct security impact (e.g. stack traces, path disclosure, directory listings, software versions, IP disclosure, 3rd party secrets)
CSV injection
HTTP Strict Transport Security Header (HSTS)
Subdomain takeover without a full working PoC
Blind SSRF without direct impact (e.g. DNS pingback)
Lack of rate-limiting, brute-forcing or captcha issues
User enumeration (email, alias, GUID, phone number)
Password requirements policies (length / complexity / reuse)
Ability to spam users (email / SMS / direct messages flooding)
Disclosed / misconfigured Google API key (including Google Maps)
Recently disclosed 0-day vulnerabilities (less than 30 days since patch release)
Password reset token leak on trusted third-party website via Referer header (eg Google Analytics, Facebook…)
Stolen secrets, credentials or information gathered from a third-party asset that we have no control over
Exposed secrets, credentials or information on an asset under our control that are not applicable to the program’s scope

Hunting requirements

Account access

No accounts will be provided in the framework of this program but you're welcome nonetheless to self-register whenever possible on our applications.

On boost.vinci.com & vinci-groupe.profils.org:

you can freely register on the application without additional information
you MUST add extra keywords in your account details, ie Name & Surname (BugBounty, TEST)
you MUST add visible mention (IGNORE THIS, TEST) in the forms submit (eg: Ask for help to a teacher, job apply)

Please use your YesWeHack email aliases which are [https://yeswehack.com/user/my-yeswehack/email-alias](available here) for account creation.

Out of scope

Anything that is not explicitely listed in scope section

For jobs.vinci.com, depending on the job offer, the Apply button might redirect to other Web sites: ONLY vinci-groupe.profils.org is allowed and already present in the program.

User agent

Please append to your user-agent header the following value: ' -BugBounty-vinci-31337 '.

Hunters collaboration

When submitting new report, you can add up to 5 collaborators, and define the reward split ratio.

For more information, see [https://helpcenter.yeswehack.io/hunter/hunter-collaboration](help center). Note: For reports that have already been rewarded, it is not possible to redistribute the rewards.

To submit a vulnerability report, you need to login with your hunter account. /programs/vincisa-public-program/create-report