• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Forwarded to devs Incorrect nginx rules from WP Toolkit

Dmytro

Basic Pleskian
Username:

TITLE

Incorrect nginx rules from WP Toolkit

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk 18.0.47 update 5, CloudLinux 8.6 x64

PROBLEM DESCRIPTION

If you choose block access to wp-config.php or to sensitivity files you cant use url on your site like this https://***domain***/posts/wp-config-php-ultimate-guide.html

I think you should use something like wp\-config\.php instead of wp-config\.php in the nginx location regex.
Original regex looks like:

NGINX:
#extension wp-toolkit begin
    # "Block unauthorized access to wp-config.php"
    # To remove this rule, revert this security measure on each WordPress installation on this domain
    location ~* wp-config.php { deny all; }


    # "Block access to sensitive files"
    # To remove this rule, revert this security measure on each WordPress installation on this domain
    location ~* "(?:wp-config\.bak|\.wp-config\.php\.swp|(?:readme|license|changelog|-config|-sample)\.(?:php|md|txt|htm|html))" {
        return 403;
    }

STEPS TO REPRODUCE

  1. Go to WordPress, choose the installation you want to secure, and then, on the installation card,
    click the message “Fix security”
  2. Wait for WP Toolkit to display the security measures you can
    apply.
  3. Select "Block unauthorized access to wp-config.php" and/or "Block access to sensitive files"
  4. Create any file/url on website starts with wp-config and open in browser

ACTUAL RESULT

403 error

EXPECTED RESULT

no errors

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Thank you. Submitted as [PPS-13875]. You can provide this ID to support staff in case you have specific questions on the case.
 
Back
Top