Skip to content

WP Engine bug bounty programs

wpengine.com Updated

WP Engine runs two public programs: an Intigriti disclosure program with no cash rewards and an Intigriti bug bounty paying up to €2,500 (paused).

Top reward
Not published
Programs
2
1 pays cash
Targets in scope
21
3 types, deduplicated
Last change
None yet
Tracked since Nov 2026

Where to report

2 programs, side by side. Report where the affected target is in scope; when two programs cover it, pick the one that pays more.

Start here

WP Engine VDP

Intigriti · A disclosure program: you report for credit, not cash.

Amounts are the top reward per severity in the currency each program pays. Green marks the highest per severity. First response is the platform's measured average when it publishes one, else what the policy promises.

What is in scope

21 targets across all 2 programs, each listed once with the programs that cover it. 3 excluded.

No target matches. Try part of a host name, such as the company name.

Out of scope 3

Don't test these. A program can exclude a host another program covers; the program you report to decides.

  • https://getflywheel.com/schedule-a-demo

    WP Engine VDP

  • https://wpengine.com/contact

    WP Engine VDP

  • marketing.nitropack.io

    WP Engine Bug Bounty

Recent changes

Reward and scope changes across every WP Engine program, newest first.

No changes recorded yet. New targets and reward moves show up here and in the RSS feed.

Recent CVEs

Published vulnerabilities in WP Engine products, from the NVD.

Search NVD
  • CVE-2024-3901 Medium

    The Genesis Blocks WordPress plugin through 3.1.3 does not properly escape attributes provided to some of its custom blocks, making it possible for users allowed to write posts (like those with the contributor role) to conduct Stored XSS attacks.

  • CVE-2024-3901 Medium

    The Genesis Blocks WordPress plugin through 3.1.3 does not properly escape attributes provided to some of its custom blocks, making it possible for users allowed to write posts (like those with the contributor role) to conduct Stored XSS attacks.

  • Cross-site scripting vulnerability exists in Advanced Custom Fields versions 6.3.5 and earlier and Advanced Custom Fields Pro versions 6.3.5 and earlier. If an attacker with the 'capability' setting privilege which is set in the product settings stores an arbitrary script in the field label, the script may be executed on the web browser of the logged-in user with the same privilege as the attacker

  • Cross-site scripting vulnerability exists in Advanced Custom Fields versions 6.3.5 and earlier and Advanced Custom Fields Pro versions 6.3.5 and earlier. If an attacker with the 'capability' setting privilege which is set in the product settings stores an arbitrary script in the field label, the script may be executed on the web browser of the logged-in user with the same privilege as the attacker

  • CVE-2024-3563 Medium

    The Genesis Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Sharing block in all versions up to, and including, 3.1.3 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute

  • CVE-2024-3563 Medium

    The Genesis Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Sharing block in all versions up to, and including, 3.1.3 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute

  • CVE-2024-2761 Medium

    The Genesis Blocks WordPress plugin before 3.1.3 does not properly escape data input provided to some of its blocks, allowing using with at least contributor privileges to conduct Stored XSS attacks.

  • CVE-2024-2761 Medium

    The Genesis Blocks WordPress plugin before 3.1.3 does not properly escape data input provided to some of its blocks, allowing using with at least contributor privileges to conduct Stored XSS attacks.

About this page

This page gathers every public program listed under wpengine.com: platform programs, self-hosted policies and security.txt contacts. Each program's own policy decides what is in scope and what it pays; check it before you test.

Something wrong or missing? Report a correction.