Skip to main content
Advanced Search
Search Terms
Content Type

Exact Matches
Tag Searches
Date Options
Updated after
Updated before
Created after
Created before

Search Results

395 total results found

Unencrypted Telnet Server

XSLT Injection

Apache webserver

Browsable Web Directories

Plesk

Browsable Web Directories

Microsoft IIS webserver

Content Security Policy (CSP) Header No...

Nginx webserver

Content Security Policy (CSP) Header No...

Apache webserver

Content Security Policy (CSP) Header No...

Plesk

Content Security Policy (CSP) Header No...

WordPress

Content Security Policy (CSP) Header No...

Joomla

Content Security Policy (CSP) Header No...

Drupal

Content Security Policy (CSP) Header No...

Microsoft IIS webserver

Cookie with SameSite Attribute None

Nginx webserver

Cookie with SameSite Attribute None

Apache webserver

Cookie with SameSite Attribute None

Plesk

Cookie with SameSite Attribute None

WordPress

Cookie with SameSite Attribute None

Joomla

Cookie with SameSite Attribute None

Drupal

Cookie with SameSite Attribute None

Generic / Developer guidance

Cross-Domain JavaScript Source File Inc...

WordPress

Cross-Domain JavaScript Source File Inc...

Joomla

Cross-Domain JavaScript Source File Inc...

Drupal

Cross-Domain JavaScript Source File Inc...

Remediation Steps

Browsable Web Directories Apache webserver

Follow the steps below to remediate this finding on Apache webserver. Remove the Indexes option from the Directory directive in your Apache configuration:<Directory /var/www/html> Options -Indexes </Directory>Alternatively, add the following to your .htaccess ...

Remediation Steps

Browsable Web Directories Plesk

Follow the steps below to remediate this finding on Plesk. Log in to Plesk.Go to Domains > your domain > Apache & nginx Settings.Under "Additional Apache directives", add:Options -IndexesClick Apply.

Remediation Steps

Content Security Policy (CSP) Header No... Microsoft IIS webserver

Follow the steps below to remediate this finding on Microsoft IIS webserver. Open IIS Manager.Select your website.Double-click HTTP Response Headers.Click Add in the Actions pane and enter:NAME: Content-Security-PolicyVALUE: default-src 'self'; script-src 'sel...

Remediation Steps

Content Security Policy (CSP) Header No... Nginx webserver

Follow the steps below to remediate this finding on Nginx webserver. In your nginx.conf server block, add:add_header Content-Security-Policy "default-src 'self'; script-src 'self'; object-src 'none';" always;Reload Nginx:sudo systemctl reload nginxNote: Start ...

Remediation Steps

Content Security Policy (CSP) Header No... Apache webserver

Follow the steps below to remediate this finding on Apache webserver. Ensure mod_headers is enabled:sudo a2enmod headersAdd to your apache2.conf or VirtualHost configuration:Header always set Content-Security-Policy "default-src 'self'; script-src 'self'; obje...

Remediation Steps

Content Security Policy (CSP) Header No... Plesk

Follow the steps below to remediate this finding on Plesk. Log in to the Plesk control panel.Navigate to Domains > your domain > Apache & nginx Settings.Under "Additional nginx directives", add:add_header Content-Security-Policy "default-src 'self'; script-src...

Remediation Steps

Content Security Policy (CSP) Header No... WordPress

Follow the steps below to remediate this finding on WordPress. Add the following to your theme's functions.php file:add_action('send_headers', function() { header("Content-Security-Policy: default-src 'self'; script-src 'self' 'unsafe-inline'; object-src 'none...

Remediation Steps

Content Security Policy (CSP) Header No... Joomla

Follow the steps below to remediate this finding on Joomla. Edit the .htaccess file in the Joomla root directory and add:<IfModule mod_headers.c> Header always set Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline'; object-src 'none...

Remediation Steps

Content Security Policy (CSP) Header No... Drupal

Follow the steps below to remediate this finding on Drupal. Install and enable the Security Kit (SecKit) module:composer require drupal/seckit drush en seckitNavigate to Admin > Configuration > System > Security Kit.Under the "Content Security Policy" section,...

Remediation Steps

Cookie with SameSite Attribute None Microsoft IIS webserver

Follow the steps below to remediate this finding on Microsoft IIS webserver. In web.config, use URL Rewrite to append SameSite=Lax or SameSite=Strict to Set-Cookie headers:<rewrite> <outboundRules> <rule name="Add SameSite" preCondition="No SameSite"> <match s...

Remediation Steps

Cookie with SameSite Attribute None Nginx webserver

Follow the steps below to remediate this finding on Nginx webserver. Use the proxy_cookie_flags directive (nginx >= 1.19.3):proxy_cookie_flags ~ SameSite=Lax;For older versions, use the lua-nginx-module or configure the application itself to set the correct Sa...

Remediation Steps

Cookie with SameSite Attribute None Apache webserver

Follow the steps below to remediate this finding on Apache webserver. Ensure mod_headers is enabled:sudo a2enmod headersAdd to your VirtualHost or .htaccess:Header always edit Set-Cookie (.*) "$1; SameSite=Lax"Reload Apache:sudo systemctl reload apache2

Remediation Steps

Cookie with SameSite Attribute None Plesk

Follow the steps below to remediate this finding on Plesk. Log in to the Plesk control panel.Navigate to Domains > your domain > Apache & nginx Settings.Under "Additional Apache directives", add:Header always edit Set-Cookie (.*) "$1; SameSite=Lax"Click Apply.

Remediation Steps

Cookie with SameSite Attribute None WordPress

Follow the steps below to remediate this finding on WordPress. Add the following to wp-config.php to set SameSite=Lax on the WordPress session cookie:@ini_set('session.cookie_samesite', 'Lax');For the auth cookies, add to functions.php:add_filter('set_auth_coo...

Remediation Steps

Cookie with SameSite Attribute None Joomla

Follow the steps below to remediate this finding on Joomla. In your Joomla configuration.php, set:public $cookie_domain = '';For Joomla 4+, edit libraries/src/Application/WebApplication.php or use the session configuration in Global Configuration > System > Se...

Remediation Steps

Cookie with SameSite Attribute None Drupal

Follow the steps below to remediate this finding on Drupal. In settings.php, configure the session cookie:ini_set('session.cookie_samesite', 'Lax');For Drupal 9+, add to settings.php:$settings['session_handler_class'] = '\Drupal\Core\Session\SessionHandler';Sa...

Remediation Steps

Cross-Domain JavaScript Source File Inc... Generic / Developer guidance

Follow the steps below to remediate this finding on Generic / Developer guidance. Only load JavaScript from origins you control or that you explicitly trust.Audit all <script src="..."> tags and JavaScript includes and replace any unnecessary third-party sourc...

Remediation Steps

Cross-Domain JavaScript Source File Inc... WordPress

Follow the steps below to remediate this finding on WordPress. Audit scripts enqueued via wp_enqueue_script() and remove or replace third-party CDN sources with self-hosted copies where possible.For remaining CDN scripts, add SRI hashes via the script_loader_t...

Remediation Steps

Cross-Domain JavaScript Source File Inc... Joomla

Follow the steps below to remediate this finding on Joomla. Audit scripts loaded in your template's index.php and component views.Replace remote CDN references with locally hosted copies where possible.For third-party scripts, add integrity and crossorigin att...

Remediation Steps

Cross-Domain JavaScript Source File Inc... Drupal

Follow the steps below to remediate this finding on Drupal. Audit libraries defined in *.libraries.yml files for external URLs.Replace CDN sources with local files where possible:my_library:js:/libraries/mylib/lib.min.js: {}For external sources that must remai...