Security Scan Results
https://developer.wordpress.org
Scan complete
developer.wordpress.org
Good Security
15 issues detected
Scanned 4 months ago
15
Total
0
Critical
0
High
4
Medium
WordPress version 7.0-beta2-61756 detected
WP_DEBUG is disabled (no PHP errors visible)
Missing security header: X-Content-Type-Options -- Prevents MIME-type sniffing
How to fix: Add to .htaccess: Header always set X-Content-Type-Options "nosniff" — prevents MIME-type sniffing.
Missing security header: Strict-Transport-Security -- Enforces HTTPS connections
How to fix: Add to .htaccess or nginx: Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"
Missing security header: Content-Security-Policy -- Controls resource loading
Missing security header: Referrer-Policy -- Controls referrer information
Missing security header: Permissions-Policy -- Controls browser feature access
1 of 6 security headers configured
SSL certificate valid (56 days remaining) — issued by Let's Encrypt
HTTP correctly redirects to HTTPS
User enumeration possible via REST API -- found: aaroncampbell, adamsilverstein, adamwood, atachibana, allendav
How to fix: Disable the REST API users endpoint with a plugin like Disable REST API or add a filter to block /wp/v2/users.
wp-cron.php is publicly accessible (potential DDoS vector)
/wp-cron.php
How to fix: Disable WP-Cron in wp-config.php with define("DISABLE_WP_CRON", true) and use a real server cron job instead.
Suspicious inline JavaScript: unicode-escaped strings
How to fix: Inspect this inline JavaScript carefully — obfuscated code can indicate malware injection.
1 trusted external script(s): stats.wp.com
Checked against 11 blacklist services
Want to find hidden issues?
This surface scan checks what's publicly visible. A deep scan connects via SSH to check file integrity, database injections, and hidden backdoors.
Run Deep Scan — $1