Security Scan Results

WordPress version 6.9.4 detected

Plugin 'google-language-translator' v6.0.20: Translate WordPress &#8211; Google Language Translator [google-language-translator] < 6.0.20

Plugin 'google-language-translator' v6.0.20: Translate WordPress &#8211; Google Language Translator [google-language-translator] < 6.0.20

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

HTTP correctly redirects to HTTPS

Cookies missing security flags (HttpOnly): omnFEpvaLhTeVCyi, CupHgGiheRIENXQn, XasQkxPBnSlgY_p

How to fix: Set cookie security flags in wp-config.php: @ini_set("session.cookie_httponly", 1); @ini_set("session.cookie_secure", 1); @ini_set("session.cookie_samesite", "Lax");

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.

External JS from popular domain: www.statcounter.com (Tranco rank #1,075)

How to fix: This script is from a well-known domain (ranked in the top 100K globally). Likely legitimate, but verify it matches a service you intentionally added.

External JS from popular domain: translate.google.com (Tranco rank #1)

How to fix: This script is from a well-known domain (ranked in the top 100K globally). Likely legitimate, but verify it matches a service you intentionally added.

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

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

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

2 external script(s) from popular domains (Tranco top 100K): www.statcounter.com, translate.google.com

How to fix: These scripts are from globally popular domains. They are very likely legitimate services but were not in our curated whitelist.