Security Scan Results

Plugin 'autoptimize' v3.1.14: Autoptimize [autoptimize] < 3.1.14

WP_DEBUG is disabled (no PHP errors visible)

PHP 8.2.30 detected (supported version)

X-Powered-By header exposed: PHP/8.2.30 — reveals server software

How to fix: Hide X-Powered-By header. In php.ini set expose_php = Off, or add Header unset X-Powered-By to .htaccess.

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 valid (42 days remaining) — issued by Let's Encrypt

HTTP correctly redirects to HTTPS

WordPress readme exposed (version info)

/readme.html

WordPress license file exposed

/license.txt

REST API user enumeration blocked

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 (41 occurrences)

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

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

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

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

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

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

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

1 trusted external script(s): maps.googleapis.com (Google)