Wordfence received 1,077 vulnerability submissions in July 2026, according to its Wordfence bug bounty report, published October 29. The figure covers reports sent to the program, not just confirmed vulnerabilities: Wordfence classified 243 as in scope, while 610 were rejected and 207 were duplicates.
For WordPress site owners and plugin developers, that distinction matters. The report offers a view into what researchers submitted, what the program accepted and which issue types attracted the largest rewards. It is not a list of 1,077 newly disclosed security flaws.
What the Wordfence bug bounty report counts
Wordfence says its Threat Intelligence team reviews submissions, validates vulnerabilities and coordinates responsible disclosure with software vendors. The July report lists 281 active researchers, down 8.2% from the prior month, while total submissions rose 1.0%.
Of the 1,077 submissions, 243 were marked in scope, 17 out of scope, 610 rejected and 207 duplicates. Those categories add up to the full submission total. The large rejected and duplicate counts are a useful reminder that a submission is a report to assess, not automatically a verified vulnerability.
The report also records 84 high-threat findings, up 44.8% from the previous month, and 73 “common and dangerous” findings, up 62.2%. Wordfence defines the first group as issues such as arbitrary file uploads or remote code execution that can be exploited by unauthenticated or low-level authenticated users in software with at least 25 active installations. Its second group covers stored cross-site scripting and SQL injection meeting a 500-install threshold and similar access requirements.
Upload flaws led total bounty payments
Wordfence reported $51,183 in July bounty payments. The highest single award was $15,600, and the report gives an average of $210.63 per validated, in-scope submission.
Unrestricted uploads of files with dangerous types led total rewards among the in-scope vulnerability classes, bringing in $21,909 across 18 submissions. Stored cross-site scripting appeared more often, with 80 submissions and $13,415 in total rewards. SQL injection had 18 submissions and $2,968 in rewards.
That contrast is more informative than a single “most common flaw” label. Stored XSS produced the highest submission count in the report’s top-ten list, while upload flaws produced the highest total payout. Wordfence’s figures describe its program’s in-scope submissions and awards, not every WordPress vulnerability reported or fixed during July.
Unauthenticated reports made up the largest access group
Wordfence lists 163 in-scope vulnerabilities as unauthenticated and 60 as requiring subscriber-level access. Another 14 required unauthenticated access plus a user-interface interaction, and four were grouped under “Custom.” The table does not account for all 243 in-scope findings in those listed access categories, so they should not be treated as a complete breakdown.
The top award went to research on an unauthenticated arbitrary file upload in Elementor Pro, affecting versions up to 4.2.1. Wordfence lists a $15,600 payment and an install count of 5 million. Other top-five awards covered Forminator Forms, User Profile Builder, Independent Analytics and Unlimited Elements for Elementor.
What site owners should take from July’s figures
The report is a snapshot of one security research program, with submissions dated July and publication on October 29. It does not establish that every issue was exploitable in the same way, that all affected software remains vulnerable, or that the submission totals predict future attacks.
It does give administrators a practical reason to keep plugin and theme maintenance on a regular schedule. Wordfence says validated findings are disclosed to vendors and that its team may add firewall rules where appropriate. That process supports disclosure and protection, but it does not replace applying a vendor’s security update when one is available.
For developers, the report points to a clear review priority: check file uploads and authorization boundaries, including code paths available to users with limited permissions. That is an inference from the report’s vulnerability categories and access-level counts, not a claim that every plugin has those defects.
FAQ
How many WordPress vulnerability submissions did Wordfence receive in July 2026?
Wordfence reported 1,077 submissions to its bug bounty program in July 2026. It classified 243 as in scope, 610 as rejected and 207 as duplicates, among other categories.
Were all 1,077 submissions confirmed vulnerabilities?
No. The report separates submissions from in-scope findings and lists rejected, duplicate and out-of-scope reports. A submission count should not be read as the number of validated or publicly disclosed vulnerabilities.
Which vulnerability type earned the most in July?
Unrestricted file uploads with dangerous file types generated the highest total rewards in the report, at $21,909 across 18 in-scope submissions. Stored cross-site scripting had the most submissions among the listed types, with 80.
Next step: review your WordPress plugins and themes for available security updates, then confirm that your site is running patched versions.