Search Results

Follow the steps below to remediate this finding on Nginx webserver. In your nginx.conf or server block, add generic error page directives:error_page 500 502 503 504 /50x.html; location = /50x.html { root /usr/share/nginx/html; internal; }For PHP-FPM, ensure d...

Follow the steps below to remediate this finding on Apache webserver. In your Apache configuration or .htaccess file, configure custom error pages:ErrorDocument 500 /errors/500.html ErrorDocument 403 /errors/403.html ErrorDocument 404 /errors/404.htmlIn php.in...

Follow the steps below to remediate this finding on WordPress. In wp-config.php, disable debug output:define('WP_DEBUG', false); define('WP_DEBUG_DISPLAY', false); define('WP_DEBUG_LOG', false);If the site previously had WP_DEBUG enabled, ensure the debug.log ...

Follow the steps below to remediate this finding on Joomla. In the Joomla Administrator panel, go to System > Global Configuration > Server tab.Set Error Reporting to None.Also set Force HTTPS to Entire site if not already done.Click Save.

Follow the steps below to remediate this finding on Drupal. In the Drupal Administrator panel, go to Administration > Configuration > Development > Logging and errors.Set "Error messages to display" to None.Ensure display_errors is disabled in php.ini on the s...

Follow the steps below to remediate this finding on Generic / Developer guidance. Redirects that carry large response bodies may expose sensitive data in the Location header or response body before the browser follows the redirect.Audit all redirect responses ...