نسخههای متأثر
- نسخههای متأثر
- <=3.6.1 || >=3.7 <=3.7.39 || >=3.8 <=3.8.39 || >=3.9 <=3.9.37 || >=4.0 <=4.0.36 || >=4.1 <=4.1.36 || >=4.2 <=4.2.33 || >=4.3 <=4.3.29 || >=4.4 <=4.4.28 || >=4.5 <=4.5.27 || >=4.6 <=4.6.24 || >=4.7 <=4.7.24 || >=4.8 <=4.8.20 || >=4.9 <=4.9.21 || >=5.0 <=5.0.17 || >=5.1 <=5.1.14 || >=5.2 <=5.2.16 || >=5.3 <=5.3.13 || >=5.4 <=5.4.11 || >=5.5 <=5.5.10 || >=5.6 <=5.6.9 || >=5.7 <=5.7.7 || >=5.8 <=5.8.5 || >=5.9 <=5.9.4 || >=6.0 <=6.0.2
- نسخهٔ اصلاحشده
- 3.7.40 · 3.8.40 · 3.9.38 · 4.0.37 · 4.1.37 · 4.2.34 · 4.3.30 · 4.4.29 · 4.5.28 · 4.6.25 · 4.7.25 · 4.8.21 · 4.9.22 · 5.0.18 · 5.1.15 · 5.2.17 · 5.3.14 · 5.4.12 · 5.5.11 · 5.6.10 · 5.7.8 · 5.8.6 · 5.9.5 · 6.0.3
شرح آسیبپذیری
WordPress Core in versions up to 6.0.3 had a weakness in how Share User Instances were handled. This fix appears to have been necessary to safely use the wp_set_current_user( 0 ); method to patch the previously mentioned XSS and CSRF in wp-mail.php and wp-trackback.php vulnerabilities. The previous functionality may have resulted in third party plugins or themes using the wp_set_current_user function in a way that could lead to privilege escalation and users being able to perform more actions than originally intended.
پیوندها
گزارشدهندگان
- Ben Bidner
- Alex Concha

