CVE & Vulnerability Research

Focused, evidence-backed security research

I work as a CVE researcher and WordPress security researcher, uncovering real, high-impact vulnerabilities in WordPress plugins and reporting them through coordinated disclosure. Every finding below is documented in an authoritative, third-party advisory — this is verifiable research, not a list of identifiers.

The bulk of my work is credited on the Wordfence and Patchstack platforms, where I currently rank #7 worldwide all-time on Wordfence and among the top 8 on Patchstack — and I am #1 in France, the French researcher with the most CVEs.

Wordfence lists 712 all-time discoveries credited to me — 700 unique CVEs. The chart below shows the severity breakdown, including 26 Critical and 75 High findings, with CVSS scores from the published advisories:

Selected findings

Representative Critical (CVSS 9.8) discoveries — unauthenticated remote code execution, privilege escalation, PHP object injection and SQL injection — each documented in an authoritative Wordfence advisory:

Browse all 700+ CVEs →

Notable Wordfence advisories

High-impact, unauthenticated findings published as Wordfence advisories — including privilege escalation and remote code execution:

Vulnerability classes

My research regularly covers the following classes of vulnerability, with a particular focus on access-control and authentication failures that lead to full compromise:

• PHP Object Injection
• SQL Injection
• Remote Code Execution
• Privilege Escalation
• Broken Access Control
• Cross-Site Scripting
• Cross-Site Request Forgery
• Sensitive Data Exposure

Where the research is credited

Independent vulnerability databases and security vendors maintain public records of my credited discoveries. These are authoritative references for the work:

• Wordfence Researcher profile · all-time ranking (opens an external site)
• Patchstack Researcher profile · Top 8 all-time (opens an external site)
• dbugs Researcher leaderboard · #6 by total CVSS (opens an external site)
• WPScan Credited vulnerability record (opens an external site)
• GCVE CVE credits (opens an external site)
• CIRCL CVE credits (opens an external site)
• TryHackMe Learning profile · 2000+ day streak (opens an external site)
• LinkedIn Professional profile (opens an external site)
• Mikadmin Technical write-ups & notes (opens an external site)

Methodology

• Manual source-code auditing — reading plugin code rather than relying only on automated scanning.
• White-box research — analysing data flows, capability checks and nonce handling to find broken access control and privilege escalation.
• Responsible disclosure — coordinating with vendors and platforms so that patches ship before public details.

See my WordPress security specialization for more on the approach.