Описание
In in wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php in WordPress 3.7 to 5.3.0, authenticated users who do not have the rights to publish a post are able to mark posts as sticky or unsticky via the REST API. For example, the contributor role does not have such rights, but this allowed them to bypass that. This has been patched in WordPress 5.3.1, along with all the previous WordPress versions from 3.7 to 5.3 via a minor release.
Ссылки
- Patch
- Third Party Advisory
- Third Party Advisory
- Mailing ListThird Party Advisory
- Release NotesVendor Advisory
- Release NotesThird Party Advisory
- Third Party Advisory
- Third Party Advisory
- Patch
- Third Party Advisory
- Third Party Advisory
- Mailing ListThird Party Advisory
- Release NotesVendor Advisory
- Release NotesThird Party Advisory
- Third Party Advisory
- Third Party Advisory
Уязвимые конфигурации
Одно из
EPSS
4.3 Medium
CVSS3
5 Medium
CVSS2
Дефекты
Связанные уязвимости
In in wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php in WordPress 3.7 to 5.3.0, authenticated users who do not have the rights to publish a post are able to mark posts as sticky or unsticky via the REST API. For example, the contributor role does not have such rights, but this allowed them to bypass that. This has been patched in WordPress 5.3.1, along with all the previous WordPress versions from 3.7 to 5.3 via a minor release.
In in wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.ph ...
WordPress before 5.3.1 allowed an unauthenticated user to make a post sticky through the REST API because of missing access control in wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php.
Уязвимость функции class-wp-rest-posts-controller системы управления содержимым сайта WordPress, связанная с небезопасным управлением привилегиями, позволяющая нарушителю оказать воздействие на целостность данных
EPSS
4.3 Medium
CVSS3
5 Medium
CVSS2