← All insights
Security & Trust

The Most Popular Frameworks Are the Least Secure. The Data Is Unambiguous.

Plot detection volume against CVE count. The line goes one direction.

· 5 min read
Share on X LinkedIn
The Most Popular Frameworks Are the Least Secure. The Data Is Unambiguous.

Across the 25 frameworks WebPulse tracks, there is a clear inverse correlation between detection volume and security score. The most detected frameworks have the most CVEs. The least detected have the fewest. The relationship is not subtle.

The Data

74.3% of detections, 18,005 CVEs, security score: 22/100
WordPress
Source: WebPulse detection + NVD/NIST (June 2026)
3.5% of detections, 800+ CVEs, security score: 28/100
Joomla
Source: WebPulse detection + NVD/NIST (June 2026)
2.8% of detections, 400+ CVEs, security score: 35/100
Drupal
Source: WebPulse detection + NVD/NIST (June 2026)
<1% of detections, 3 CVEs, security score: 95/100
Astro
Source: WebPulse detection + NVD/NIST (June 2026)

Causation, Not Just Correlation

The relationship isn't just 'popular things get more scrutiny.' The architecture matters. WordPress, Joomla, and Drupal are monolithic PHP CMSs with plugin ecosystems, database dependencies, and server-side execution on every request. Each component is an attack surface. Each plugin is a supply chain dependency.

Modern frameworks like Astro, Hugo, and Eleventy produce static output. No database, no plugins, no server-side execution. The attack surface is fundamentally smaller — not because fewer people are looking, but because there's less to find.

The Structural Argument

This is not a 'PHP is bad' argument. Laravel scores 92/100 despite being PHP. The difference is architecture: Laravel enforces input validation, parameterized queries, and CSRF protection by default. WordPress leaves these to individual plugin developers — and 60,000 plugin developers make 60,000 different security decisions.

Share this insight
More insights