CVE-2023-288374.9MediumCWE-770

CVE-2023-28837: Wagtail vulnerable to denial-of-service via memory exhaustion when uploading large files

wagtail

Affected: wagtail · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

1.1%probability of exploitation in the next 30 days

65th percentile

050100

Higher than 65% of scored CVEs

4.9MediumCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

Wagtail is an open source content management system built on Django. Prior to versions 4.1.4 and 4.2.2, a memory exhaustion bug exists in Wagtail's handling of uploaded images and documents. For both images and documents, files are loaded into memory during upload for additional processing. A user with access to upload images or documents through the Wagtail admin interface could upload a file so large that it results in a crash of denial of service. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin. It can only be exploited by admin users with permission to upload images or documents. Image uploads are restricted to 10MB by default, however this validation only happens on the frontend and on the backend after the vulnerable code. Patched versions have been released as Wagtail 4.1.4 and Wagtail 4.2.2). Site owners who are unable to upgrade to the new versions are encouraged to add extra protections outside of Wagtail to limit the size of uploaded files.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

wagtail · wagtail< 4.1.4; >= 4.2, < 4.2.2

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Allocation Without Limits · Denial of Service
Vendor: wagtail
Published: April 2023
Band: Possible (1 to 10%), April 2023

CoverageNo articles yet

No CyberSIXT article names CVE-2023-28837 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.