Security Scan Results

WordPress 7.0.2: WordPress Core 6.9 - 7.0.1 - Remote Code Execution via REST API Batch Request Route Confusion

WordPress version 7.0.2 detected

WP_DEBUG is disabled (no PHP errors visible)

Missing security header: X-Frame-Options -- Prevents clickjacking attacks

How to fix: Add to .htaccess: Header always set X-Frame-Options "SAMEORIGIN" — prevents clickjacking attacks.

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

SSL certificate expires in 21 days

How to fix: Your SSL certificate expires soon. Set up auto-renewal or renew manually.

HTTP correctly redirects to HTTPS

WordPress readme exposed (version info)

/readme.html

WordPress license file exposed

/license.txt

User enumeration possible via REST API -- found: admin, agaty-kaliatzi, aleksandra-gracjasz, aleksandra-pietrusiak, andrzej-gorczynski

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: heavy unicode-escaped strings (32 occurrences)

How to fix: Inspect this inline JavaScript carefully — obfuscated code can indicate malware injection.

Suspicious inline JavaScript: heavy unicode-escaped strings (36 occurrences)

How to fix: Inspect this inline JavaScript carefully — obfuscated code can indicate malware injection.

Suspicious inline JavaScript: atob() base64 decoding

How to fix: Inspect this inline JavaScript carefully — obfuscated code can indicate malware injection.

1 trusted external script(s): www.googletagmanager.com (Google)