Craft CMS up to 4.16.16/5.8.20 Database Backup allocation of resources

Summaryinfo

A vulnerability identified as critical has been detected in Craft CMS up to 4.16.16/5.8.20. This issue affects some unknown processing of the component Database Backup Handler. This manipulation causes allocation of resources. This vulnerability is tracked as CVE-2025-68456. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in Craft CMS up to 4.16.16/5.8.20. Affected by this vulnerability is some unknown functionality of the component Database Backup Handler. The manipulation with an unknown input leads to a allocation of resources vulnerability. The CWE definition for the vulnerability is CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Craft is a platform for creating digital experiences. In versions 5.0.0-RC1 through 5.8.20 and 3.0.0 through 4.16.16, unauthenticated users can trigger database backup operations via specific admin actions, potentially leading to resource exhaustion or information disclosure. Users should update to the patched versions (5.8.21 and 4.16.17) to mitigate the issue. Craft 3 users should update to the latest Craft 4 and 5 releases, which include the fixes.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2025-68456 since 12/17/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.

Upgrading to version 4.16.17 or 5.8.21 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch f83d4e0c6b906743206b4747db4abf8164b8da39 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-0825). Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• Content Management System

Vendor

• Craft

Name

• CMS

Version

• 4.16.0
• 4.16.1
• 4.16.2
• 4.16.3
• 4.16.4
• 4.16.5
• 4.16.6
• 4.16.7
• 4.16.8
• 4.16.9
• 4.16.10
• 4.16.11
• 4.16.12
• 4.16.13
• 4.16.14
• 4.16.15
• 4.16.16
• 5.8.0
• 5.8.1
• 5.8.2
• 5.8.3
• 5.8.4
• 5.8.5
• 5.8.6
• 5.8.7
• 5.8.8
• 5.8.9
• 5.8.10
• 5.8.11
• 5.8.12
• 5.8.13
• 5.8.14
• 5.8.15
• 5.8.16
• 5.8.17
• 5.8.18
• 5.8.19
• 5.8.20

License

• free

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion