• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • 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.

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