CYBERSECURITYTRACKER
TRACKING6,506 stories in this site build1,309 vulnerability news stories in this site build
Permanent story citation

The Future of The Patchstack Bug Bounty Program

This page keeps the story as Cybersecurity Tracker first published it. If the tracker later corrects it, the correction appears below the original and never replaces it.

Back to newsStory 6281

As cited

Copy frozen at (site build).

vulnerabilities

The Future of The Patchstack Bug Bounty Program

Patchstack announced significant changes to its bug bounty program effective June 1, 2026, in response to a surge in low-impact and duplicate submissions attributed to artificial intelligence (AI)-assisted vulnerability research. The new rules narrow scope to zero-day vulnerabilities, unauthenticated or subscriber-role exploits, specific vulnerability types with strict conditions, and Patchstack mVDP software, while introducing temporary bans for researchers submitting untested or AI-generated findings that violate program criteria.

Why it matters: WordPress plugin and theme developers relying on Patchstack for vulnerability coordination must understand the narrower scope and new submission requirements, while security researchers participating in the program need to align their approach with stricter impact thresholds to avoid rejections and bans.

Source published
First seen by Cybersecurity Tracker

Source attribution

Correction

Correction recorded as of .

vulnerabilities

The Future of The Patchstack Bug Bounty Program

Patchstack announced significant changes to its bug bounty program effective June 1, 2026, in response to a surge in low-impact and duplicate submissions attributed to artificial intelligence (AI)-assisted vulnerability research. The new rules narrow scope to zero-day vulnerabilities, unauthenticated or subscriber-role exploits, specific vulnerability types with strict conditions, and Patchstack mVDP software, while introducing temporary bans for researchers submitting untested or AI-generated findings that violate program criteria.

Why it matters: WordPress plugin and theme developers relying on Patchstack for vulnerability coordination must understand the narrower scope and new submission requirements, while security researchers participating in the program need to align their approach with stricter impact thresholds to avoid rejections and bans.

VendorsWordPress
Source published
First seen by Cybersecurity Tracker

Source attribution

Glossary