In April 2026, the Wordfence Bug Bounty Program received 1288 vulnerability submissions from our growing community of security researchers working to improve the overall security posture of the WordPress ecosystem. These submissions are reviewed, triaged, and processed by the Wordfence Threat Intelligence team, with validated vulnerabilities responsibly disclosed to vendors, often through the Wordfence Vulnerability Management Portal – a free service for all WordPress vendors, and protected through the Wordfence Firewall where appropriate.
Our mission with the Wordfence Bug Bounty Program is to engage the broader security community in identifying and responsibly disclosing vulnerabilities in WordPress plugins and themes, so we can work with vendors to get them patched before attackers discover them. This collaborative effort enables Wordfence to accelerate patch adoption, provide early protection to millions of websites, and ensure that high-quality vulnerability intelligence reaches the WordPress ecosystem as efficiently as possible. It also ensures that we are able to remediate vulnerabilities before attackers are able to discover them and start exploiting them. That is why we reward researchers for valid submissions, and why we remain committed to processing every report with transparency, accuracy, and urgency.
Join the Wordfence Bug Bounty Program
Help secure the WordPress ecosystem while earning rewards for your security research.
We’re actively seeking skilled researchers to identify vulnerabilities in WordPress plugins and themes, with prompt payments and transparent processes.
As the most comprehensive and highest-quality WordPress vulnerability program, the Wordfence Bug Bounty Program plays a critical role in helping site owners, developers, and hosting providers stay ahead of emerging threats at all stages of the open source lifecycle.
In this report, we highlight key metrics of the Bug Bounty Program from April 2026, recognize the researchers contributing to WordPress security, and provide insight into the vulnerabilities uncovered and addressed.
If you’re interested in joining the program or learning more about how we responsibly manage disclosures and protect WordPress users, visit the Bug Bounty Program page.
WordPress Software Vendors – Sign Up For Free Centralized Management of all Vulnerabilities in Your Software
Wordfence provides a completely free vulnerability management portal for WordPress Software vendors to easily track and manage all vulnerabilities submitted to the Wordfence Bug Bounty Program, and added to the Wordfence Intelligence Vulnerability Database.
This portal streamlines and enhances the repsonsible disclosure process so you can secure your customers faster.
Program Submission Highlights – April 2026
The Wordfence Bug Bounty Program is designed for momentum: rapid triage of critical issues, clear feedback, and fast, fair rewards. Each submission moves through our standardized workflow of validation, vendor coordination, patch verification, and firewall coverage where applicable, so research translates into real-world protection quickly.
Real-Time Protection Impact
Every vulnerability disclosed through this program is a threat you don’t have to face blindly. Our researchers uncover and report vulnerabilities before they can be exploited, and Wordfence Premium, Care and Response users get protection in real-time through our firewall. Free users are protected in 30 days.
Behind the numbers is meaningful impact for site owners. The issues surfaced here inform new firewall rules, strengthen our detection logic, and help vendors ship safer releases. If you’re new to bounty hunting, this is a great place to start: we publish scope clearly, pay promptly, and credit the work that keeps WordPress secure.
Total Submissions
Active Researchers
High Threat
Common & Dangerous
WAF Rules Released
Vulnerability Focus Areas
- High Threat Vulnerabilities: Issues that could result in full site compromise, such as Arbitrary File Uploads or Remote Code Execution. Must be exploitable by unauthenticated or low-level authenticated attackers with software having 25+ active installations.
- Common & Dangerous: Stored Cross-Site Scripting and SQL Injection vulnerabilities exploitable by unauthenticated or low-level authenticated attackers. Software must have 500+ active installations.
Bounty Insights – April 2026
Our research powers real investment back into the community. This section totals bounties and bonuses paid for the month and showcases standout findings. Our philosophy is simple: reward high-quality, responsibly disclosed research that measurably reduces risk for WordPress users.
Total Bounties Awarded
Average Bounty Per Submission
Highest Single Bounty
Top 5 Bounties Awarded
| Vulnerability | Bounty | Install Count |
|---|---|---|
| Slider Revolution 7.0.0 – 7.0.10 – Authenticated (Subscriber+) Arbitrary File Upload via _get_media_url | $4,914.00 | 5000000 |
| Avada (Fusion) Builder <= 3.15.2 – Unauthenticated Remote Code Execution via PHP Function Injection via ‘render_logics’ Shortcode Attribute via Widget AJAX Handler | $2,600.00 | 968000 |
| Unauthenticated Arbitrary File Upload (In Disclosure) | $1,300.00 | 30000 |
| Frontend Admin by DynamiApps <= 3.29.2 – Unauthenticated Privilege Escalation via Form Configuration Injection | $975.00 | 9000 |
| Slider Revolution 7.0 – 7.0.10 – Authenticated (Subscriber+) Sensitive Information Disclosure | $960.00 | 5000000 |
Want to earn more? Read the scope carefully, target high-threat classes, and include clear reproduction steps with proof of impact. We pay promptly on validated issues, and bonus multipliers may apply during limited-time promotions and challenges.
WordPress Software Vulnerability Submission Insights – April 2026
This section breaks down how reports map to our program outcomes. What’s in scope, what isn’t, and where the highest security impact typically sits. We highlight the most common in-scope vulnerability classes and the categories that yielded the largest rewards so researchers can focus their efforts where they matter most.
Authentication level and exploit preconditions drive risk and reward through our program. Unauthenticated and low-privilege paths tend to have outsized impact because they scale to more real-world compromise. Use these insights to prioritize your testing strategy and maximize both security value and bounty potential.
Total Number of Vulnerabilities Considered In Scope, Out of Scope, Rejected, or Duplicate
| In Scope | Out of Scope | Rejected | Duplicate |
|---|---|---|---|
| 180 | 165 | 572 | 371 |
Top 10 Most Commonly Submitted In-Scope Vulnerability Types
The most frequently submitted vulnerability types highlight current testing focus areas across the researcher community. These patterns often reflect both ease of discovery and prevalence in the WordPress ecosystem.
| Vulnerability Type | Total Submissions | Total Rewards | Avg. Reward |
|---|---|---|---|
| CWE 79: Improper Neutralization of Input During Web Page Generation (‘Cross-site Scripting’) | 64 | $5,600.00 | $87.50 |
| CWE 862: Missing Authorization | 12 | $1,245.00 | $103.75 |
| CWE 269: Improper Privilege Management | 11 | $4,335.00 | $394.09 |
| CWE 89: Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’) | 11 | $1,228.00 | $111.64 |
| CWE 22: Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’) | 9 | $2,491.00 | $276.78 |
| CWE 639: Authorization Bypass Through User-Controlled Key | 8 | $252.00 | $31.50 |
| CWE 434: Unrestricted Upload of File with Dangerous Type | 6 | $8,116.00 | $1,352.67 |
| CWE 266: Incorrect Privilege Assignment | 4 | $1,073.00 | $268.25 |
| CWE 640: Weak Password Recovery Mechanism for Forgotten Password | 4 | $1,360.00 | $340.00 |
| CWE 287: Improper Authentication | 3 | $894.00 | $298.00 |
Top 10 Highest Rewarded In-Scope Vulnerability Types
While some vulnerabilities appear frequently, others command premium rewards. This breakdown shows which vulnerability classes generated the highest total payouts across all submissions in those categories, indicating both severity and exploitability value.
| Vulnerability Type | Total Rewards | Total Submissions | Avg. Reward |
|---|---|---|---|
| CWE 434: Unrestricted Upload of File with Dangerous Type | $8,116.00 | 6 | $1,352.67 |
| CWE 79: Improper Neutralization of Input During Web Page Generation (‘Cross-site Scripting’) | $5,600.00 | 64 | $87.50 |
| CWE 269: Improper Privilege Management | $4,335.00 | 11 | $394.09 |
| CWE 74: Improper Neutralization of Special Elements in Output Used by a Downstream Component (‘Injection’) | $2,600.00 | 1 | $2,600.00 |
| CWE 22: Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’) | $2,491.00 | 9 | $276.78 |
| CWE 640: Weak Password Recovery Mechanism for Forgotten Password | $1,360.00 | 4 | $340.00 |
| CWE 502: Deserialization of Untrusted Data | $1,338.00 | 3 | $446.00 |
| CWE 862: Missing Authorization | $1,245.00 | 12 | $103.75 |
| CWE 89: Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’) | $1,228.00 | 11 | $111.64 |
| CWE 266: Incorrect Privilege Assignment | $1,073.00 | 4 | $268.25 |
In-Scope Vulnerability Distribution by Authentication Level
Authentication requirements directly impact real-world exploitability. Unauthenticated and subscriber-level vulnerabilities typically pose greater risk, reflected in both our prioritization and reward structure.
| Authentication Level | Total Vulnerabilities | Avg. Reward |
|---|---|---|
| Unauthenticated | 81 | $253.59 |
| Contributor | 33 | $101.87 |
| Subscriber | 32 | $418.83 |
| Author | 12 | $143.75 |
| Custom | 7 | $117.50 |
| Unauthenticated – UI Required | 5 | $161.60 |
Vulnerability Submission Install Count Spread
Install counts help us gauge blast radius. Higher install bases can move a finding into higher priority and often correlate with stronger payouts, while smaller-but-critical ecosystems still qualify when the exploitability and impact warrant it.
| Install Range | Total Vulnerabilities | Average CVSS | Avg. Reward |
|---|---|---|---|
| 1,000–49,999 | 65 | 7.63 | $170.98 |
| 100,000–999,999 | 46 | 6.26 | $349.17 |
| 50,000–99,999 | 30 | 6.34 | $93.93 |
| Off-Repo | 22 | 8.05 | $207.28 |
| 5,000,000+ | 6 | 6.26 | $1,416.40 |
| 1,000,000–4,999,999 | 4 | 7.60 | $456.50 |
| 500–999 | 3 | 6.70 | $10.67 |
| 0–499 | 2 | 8.65 | $33.00 |
Top WordPress Security Researchers – April 2026
Security is a team sport, and this leaderboard celebrates the people raising the bar. We recognize contributors by valid in-scope submissions, overall earnings, and average severity to highlight different paths to excellence.
Top 5 Researchers based on Volume of In-Scope Submissions
Volume leaders demonstrate consistent vulnerability discovery across diverse targets. These researchers excel at systematic testing and maintaining high validation rates.
| Researcher | Total Submissions | Avg. Reward |
|---|---|---|
| Rafie Muhammad | 14 | $266.00 |
| lhking | 9 | $369.22 |
| Nguyen Ngoc Duc (duc193) | 7 | $376.14 |
| Webbernaut | 6 | $248.67 |
| h0xilo | 6 | $1,161.00 |
Top 5 Researchers Based on Average CVSS of In-Scope Submissions
Quality over quantity defines these researchers who consistently identify high-severity vulnerabilities. Their average CVSS scores reflect expertise in finding critical security gaps.
| Researcher | Average CVSS | Total Submissions | Avg. Reward |
|---|---|---|---|
| Ankit Patel | 9.80 | 1 | $195.00 |
| bashu | 9.80 | 1 | $325.00 |
| snr | 9.80 | 1 | $33.00 |
| Tin Pham (TF1T) | 9.80 | 2 | $1,467.00 |
| maru | 9.80 | 1 | $455.00 |
Top 5 Researchers Based On Total Bounties Earned
Combining volume with severity, these top earners maximized their impact and rewards through strategic vulnerability research and comprehensive reporting.
| Researcher | Total Earned | Total Submissions | Avg. Reward |
|---|---|---|---|
| h0xilo | $6,966.00 | 6 | $1,161.00 |
| Rafie Muhammad | $3,724.00 | 14 | $266.00 |
| lhking | $3,323.00 | 9 | $369.22 |
| Tin Pham (TF1T) | $2,934.00 | 2 | $1,467.00 |
| Nguyen Ngoc Duc (duc193) | $2,633.00 | 7 | $376.14 |
Researchers Promoted to the Next Tier
Congratulations to the following researchers who have unlocked the next tier! Tier promotions reflect sustained performance, precision, and professionalism in disclosure. Advancing unlocks higher caps, faster reviews, and more visibility. If you’re climbing the ranks, focus on high risk vulnerabilities, keep reports crisp, attach working PoCs, and include mitigation notes vendors can ship quickly.
Elite Researcher Tier (1337)
Resourceful Researcher Tier
Current WordPress Bug Bounty Program Promotions
As part of our Bug Bounty Program, we regularly launch special promotions that boost bounty rewards and expand research scope. These initiatives are designed to reinforce our mission: delivering the highest quality vulnerability intelligence while encouraging researchers to focus on the discoveries that have the greatest positive impact on the WordPress ecosystem.
At the same time, we also look for promotions that give researchers opportunities to sharpen their skills, take on new challenges, and continue growing into the best of the best in WordPress security research. We often supplement these with educational material for researchers to learn and apply their skills during these promotions.
Below, you’ll find details on all currently active challenges—including timelines and a quick overview of each promotion.
No promotions currently running.New to promotions? Start by confirming the software and version range are in scope, validate exploitability on a clean test environment, and submit with clear steps, affected code paths, and impact. Promotions are perfect opportunities for both new and seasoned researchers to maximize earnings while driving faster patch adoption. And remember, you can always check what’s in-scope and out-of-scope by using the Wordfence bounty estimator.
Critical WordPress Software Vulnerability Highlights – April 2026
These case studies spotlight high-impact vulnerabilities uncovered through the program, why they matter, and how quickly protection rolled out. We share technical detail to help researchers learn, vendors harden code, and users understand why timely updates aren’t optional.
If you maintain a site, update to the patched versions listed and ensure Wordfence is active so you benefit from new firewall coverage as it ships. If you’re a researcher, use these write-ups to inform your hunt: patterns repeat, and past root causes often reappear in adjacent code.
Attackers Actively Exploiting Critical Vulnerability in Ninja Forms – File Upload Plugin
Ninja Forms – File Upload <= 3.3.26 – Unauthenticated Arbitrary File Upload
Sélim Lanouar (whattheslime)
$2,145.00
The Ninja Forms – File Uploads plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the ‘NF_FU_AJAX_Controllers_Uploads::handle_upload’ function in all versions up to, and including, 3.3.26. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site’s server which may make remote code execution possible. Note: The vulnerability was partially patched in version 3.3.25 and fully patched in version 3.3.27.
Read the complete vulnerability analysis
Attackers Actively Exploiting Critical Vulnerability in Kali Forms Plugin
Kali Forms <= 2.4.9 – Unauthenticated Remote Code Execution via form_process
ISMAILSHADOW
$2,145.00
The Kali Forms plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 2.4.9 via the ‘form_process’ function. This is due to the ‘prepare_post_data’ function mapping user-supplied keys directly into internal placeholder storage, combined with the use of ‘call_user_func’ on these placeholder values. This makes it possible for unauthenticated attackers to execute code on the server.
50,000 WordPress Sites affected by Arbitrary File Upload Vulnerability in Ninja Forms – File Upload WordPress Plugin
Ninja Forms – File Upload <= 3.3.26 – Unauthenticated Arbitrary File Upload
Sélim Lanouar (whattheslime)
$2,145.00
The Ninja Forms – File Uploads plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the ‘NF_FU_AJAX_Controllers_Uploads::handle_upload’ function in all versions up to, and including, 3.3.26. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site’s server which may make remote code execution possible. Note: The vulnerability was partially patched in version 3.3.25 and fully patched in version 3.3.27.
200,000 WordPress Sites Affected by Arbitrary File Deletion Vulnerability in Perfmatters WordPress Plugin
Perfmatters <= 2.5.9.1 – Authenticated (Subscriber+) Arbitrary File Deletion via ‘delete’ Parameter
h0xilo
$3,726.00
The Perfmatters plugin for WordPress is vulnerable to arbitrary file deletion via path traversal in all versions up to, and including, 2.5.9.1. This is due to the `PMCS::action_handler()` method processing the `$_GET[‘delete’]` parameter without any sanitization, authorization check, or nonce verification. The unsanitized filename is concatenated with the storage directory path and passed to `unlink()`. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary files on the server by using `../` path traversal sequences, including `wp-config.php` which would force WordPress into the installation wizard and allow full site takeover.
200,000 WordPress Sites Affected by Arbitrary File Move Vulnerability in MW WP Form WordPress Plugin
MW WP Form <= 5.1.0 – Unauthenticated Arbitrary File Move via move_temp_file_to_upload_dir
ISMAILSHADOW
$3,105.00
The MW WP Form plugin for WordPress is vulnerable to arbitrary file moving due to insufficient file path validation via the ‘generate_user_filepath’ function and the ‘move_temp_file_to_upload_dir’ function in all versions up to, and including, 5.1.0. This makes it possible for unauthenticated attackers to move arbitrary files on the server, which can easily lead to remote code execution when the right file is moved (such as wp-config.php). The vulnerability is only exploitable if a file upload field is added to the form and the “Saving inquiry data in database” option is enabled.
Conclusion
WordPress thrives when researchers, vendors, hosts, and site owners pull in the same direction. By funding high-quality research, coordinating responsible disclosure, and shipping firewall rules at scale, Wordfence turns findings into protection for millions of sites.
If you’re a researcher, join the program and submit your next report. If you’re a site owner, update early and often, and run Wordfence to stay ahead of emerging threats. If you’re a vendor, sign up for the vulnerability management portal to receive real-time notifications when new vulnerabilities are reported in your software. Together, we make the WordPress ecosystem safer.
The post Wordfence Bug Bounty Program Monthly Report – April 2026 appeared first on Wordfence.