In the internal audit of the WordPress patrol plug-in, the jetpack scan team found some weaknesses. Someone can buy the website. These vulnerabilities immediately disclosed version 1.7.2 to the plug-in authors who published these issues. If you are running an earlier version of the plug-in, please update it today! Read all technical details. If this problem cannot be solved, please don’t worry. Jetpack scan is provided to handle malware detection and automatic upgrade or deletion. Our team has identified various attack vectors, including local file disclosure, CSRF (cross site request forery) and XSS (reflected cross site scripting) vulnerabilities. The
The local file disclosure vulnerability is a bug that can be used by malicious users to access important information, such as the private key of a website and database credentials. The vulnerability of reflected inter site scripting and inter Site Request Forgery is a problem, which can trick attackers to click on carefully crafted malicious links and let them perform specific operations on behalf of unsuspecting users. If maliciously exploited, some of them may master the vulnerable websites of malicious individuals. Version affected by local file disclosure vulnerability: male. Apply\u filters (‘ptrn\/error\u message’, self:: $messages\u map[$\u request[‘patteron\u message’]. $patteron\u error).’ Male ‘;
Patron connect connects to the WordPress login form (wp-login.php) and allows users to authenticate on the site using a patron account. Unfortunately, some of the error log logic behind the scenario allows the user to control the input to be reflected on the login page in an undeleted state. The
To successfully exploit this vulnerability maliciously, an attacker must trick victims into accessing the Boolean lab link containing malicious JavaScript code. JavaScript runs in the victim’s browser context, so an attacker can adjust the code hidden in the link to perform all operations allowed by the user’s privileges. If the attack succeeds for the administrator, the script can take full control of the site. The version affected by XSS reflected in the Ajax job \
‘patteron_level’= > $\u request[‘patteron\attachment\patteron\u level’],
‘message’= > $message,
）;
Echo self:: make\u image\u lock\u interface ($args);
Public function make_image_lock_interface ($args = array()){
$interface = ”;
$interface. = ‘ Male ‘;
$interface. = ‘ Male × Male ‘;
$interface. = ‘ Male ‘;
$interface. = ‘ Male lock image male ‘;
$interface. = ‘ Male ‘;
$interface. = ‘ Male $male ‘;
The plug-in also uses Ajax hooks to update the pledge level required for patron users to access specified attachments. This operation can access a user account with \
Unfortunately, one of the parameters used on this Ajax endpoint was not deleted before it was reprinted to the user, so it represents the same risk as the XSS vulnerability we described earlier. Versions affected by CSRF: maleid, $option_to_toggle, true;
$new_va
