If you like DNray Forum, you can support it by - BTC: bc1qppjcl3c2cyjazy6lepmrv3fh6ke9mxs7zpfky0 , TRC20 and more...

 

Multiple Bots and High Bandwidth Could Utilize WordPress Vulnerability

Started by gnh73, Jul 30, 2022, 01:26 AM

Previous topic - Next topic

gnh73Topic starter

It is crucial to understand that exploiting this vulnerability without consent from the website owner is illegal.



 The WordPress CMS platform has a severe application layer denial-of-service (DoS) vulnerability, which enables any user to bring down most WordPress sites, even with just one machine, without requiring a vast number of computers as required by DDoS attacks.

The vulnerability (CVE-2018-6389) affects nearly all WordPress versions released over the last nine years, including the latest stable version, and remains unpatched since the WordPress Foundation refused to fix it. Israeli security researcher Barak Tawily discovered the vulnerability in the "load-scripts.php" embedded script in WordPress CMS, which was designed for administrators to help improve site performance and page loading speed.

However, the feature is accessible to everyone without authentication, making it possible for hackers to slow down target sites, cause high CPU and memory cost on servers, and attack popular WordPress websites using more bandwidth or multiple bots. Despite being outside the WordPress bug bounty application's scope, Tawily reported the DoS vulnerability to the WordPress team responsibly.
  •  

neelseofast

To resolve this issue, you can simply block access to the path and redirect access to the old path through rewrites, symlinks, try_files, etc. However, this solution may not be effective if the links include something like "/xхxxхxxхxхx", which is considered hardcore.

It is worth noting that not only load-scripts.php is located in the wp-admin folder, but also admin-ajax.php. Ajax comes through admin-ajax.php from the user. Security plugins or some other plugins may cause a request for a password to pop up for guests, although it may not happen with a bare engine. If this issue had been addressed earlier, everything would have been secured by now.
  •  

sam

I believe that approximately one-third of websites cannot be hosted on WordPress due to long parallel requests, such as those in a home page URL with random parts. Additionally, some sites may require higher hosting fees. During load testing of one project, 700 threads were used from one virtual machine, causing response times to increase from seconds to tens of seconds.

This delay is unacceptable for most users, resulting in a significant drop in website traffic. Furthermore, there could be notifications for administrators on 5xx errors and a decline in audience from 1500 people during the day to 150 people at night. This may not concern all admins, and even the sales department of an e-commerce store may not immediately notice. The overall situation regarding security is concerning.
  •  

goutammohanty

The vulnerability, identified as CVE-2018-6389, affects nearly all WordPress versions released over the last nine years, including the latest stable version. This is a shocking revelation, considering the WordPress Foundation has refused to patch this vulnerability. It's like leaving a door wide open to hackers, inviting them to wreak havoc on unsuspecting website owners.

The vulnerability is located in the "load-scripts.php" embedded script, designed to improve site performance and page loading speed for administrators. However, this feature is accessible to anyone without authentication, making it a perfect entry point for hackers. They can slow down target sites, cause high CPU and memory costs on servers, and even attack popular WordPress websites using more bandwidth or multiple bots.

It's mind-boggling that the WordPress team refused to fix this vulnerability, despite it being reported responsibly by Israeli security researcher Barak Tawily. This lack of action is a clear example of negligence, leaving millions of WordPress websites vulnerable to attack. It's like leaving a ticking time bomb, waiting to explode and cause catastrophic damage.

I'm appalled by this lack of security. It's unacceptable that a platform as popular as WordPress can be left so vulnerable. The WordPress Foundation needs to take immediate action to patch this vulnerability and ensure the security of its users. Anything less is a clear dereliction of duty.
WordPress CMS platform has a severe DoS vulnerability that needs to be addressed immediately. The lack of action from the WordPress Foundation is unacceptable, and website owners need to be aware of this vulnerability to protect their sites. It's time for the WordPress community to demand better security and hold the foundation accountable for its negligence.
  •  


If you like DNray forum, you can support it by - BTC: bc1qppjcl3c2cyjazy6lepmrv3fh6ke9mxs7zpfky0 , TRC20 and more...