Описание
In WordPress before 4.9.9 and 5.x before 5.0.1, when the Apache HTTP Server is used, authors could upload crafted files that bypass intended MIME type restrictions, leading to XSS, as demonstrated by a .jpg file without JPEG data.
| Релиз | Статус | Примечание |
|---|---|---|
| bionic | ignored | end of standard support, was needed |
| cosmic | ignored | end of life |
| devel | not-affected | 5.0.1+dfsg1-1 |
| disco | not-affected | 5.0.1+dfsg1-1 |
| eoan | not-affected | 5.0.1+dfsg1-1 |
| esm-apps-legacy/xenial | needed | |
| esm-apps/bionic | needed | |
| esm-apps/focal | not-affected | 5.0.1+dfsg1-1 |
| esm-apps/jammy | not-affected | 5.0.1+dfsg1-1 |
| esm-apps/noble | not-affected | 5.0.1+dfsg1-1 |
Показывать по
3.5 Low
CVSS2
5.4 Medium
CVSS3
Связанные уязвимости
In WordPress before 4.9.9 and 5.x before 5.0.1, when the Apache HTTP Server is used, authors could upload crafted files that bypass intended MIME type restrictions, leading to XSS, as demonstrated by a .jpg file without JPEG data.
In WordPress before 4.9.9 and 5.x before 5.0.1, when the Apache HTTP S ...
In WordPress before 4.9.9 and 5.x before 5.0.1, when the Apache HTTP Server is used, authors could upload crafted files that bypass intended MIME type restrictions, leading to XSS, as demonstrated by a .jpg file without JPEG data.
3.5 Low
CVSS2
5.4 Medium
CVSS3