• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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