• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Wordpress Dataleak (UserNames and IDs)

LTUser

Regular Pleskian
Excuse me, I do not find the right place to warn about it and it is not really a security leak.
Therefore delete the info or move it to the right place if necessary.

Test this:
https://(www.)yourdomain.tld/wp-json/wp/v2/users/

Do you get a page with UserNames and IDs

add this near Rewritebase / in your .htaccess
Code:
RewriteCond %{REQUEST_URI} (wp-json|author)
RewriteRule ^(.*)$ https://www.yourdomain.tld [F,L]

The data leak also exists if the WordPress Toolkit and the
security check classify everything as "Safe".
 
I probably had too much trust in WP.
I didn't think that these barn doors were "worldreadable".

In the meantime, WP is being pushed by goggle at the expense of forums, so you have to pay more attention to your data now, especially in WP.
 
Back
Top