Описание
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.
Релиз | Статус | Примечание |
---|---|---|
bionic | ignored | end of standard support, was needs-triage |
devel | not-affected | 5.3.2+dfsg1-1 |
disco | ignored | end of life |
eoan | ignored | end of life |
esm-apps/bionic | needs-triage | |
esm-apps/focal | not-affected | 5.3.2+dfsg1-1 |
esm-apps/jammy | not-affected | 5.3.2+dfsg1-1 |
esm-apps/noble | not-affected | 5.3.2+dfsg1-1 |
esm-apps/xenial | needs-triage | |
esm-infra-legacy/trusty | DNE |
Показывать по
Ссылки на источники
EPSS
5 Medium
CVSS2
4.3 Medium
CVSS3
Связанные уязвимости
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
5 Medium
CVSS2
4.3 Medium
CVSS3