CVE-2025-68456: CWE-770: Allocation of Resources Without Limits or Throttling in craftcms cms
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.
AI Analysis
Technical Summary
CVE-2025-68456 is a vulnerability classified under CWE-770 (Allocation of Resources Without Limits or Throttling) and CWE-202 (Information Exposure Through Data Query) affecting Craft CMS, a widely used platform for building digital experiences. The flaw exists in versions 3.0.0 through 4.16.16 and 5.0.0-RC1 through 5.8.20, where unauthenticated attackers can invoke database backup operations via specific administrative endpoints or actions. Because these operations are resource-intensive and lack proper throttling or limits, attackers can cause resource exhaustion, leading to denial of service conditions. Additionally, the backup process may expose sensitive information, resulting in potential data leakage. The vulnerability is remotely exploitable without requiring authentication or user interaction, increasing its risk profile. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), with high confidentiality and availability impacts (VC:H, VA:H), and partial temporal metrics (E:P). Although no exploits are currently known in the wild, the vulnerability's characteristics make it a credible threat. The recommended mitigation is to upgrade to patched versions 4.16.17 or 5.8.21 and later, which include fixes to enforce resource limits and prevent unauthorized backup triggering. Organizations still running vulnerable versions should implement compensating controls such as restricting access to admin endpoints, monitoring for unusual backup activity, and rate limiting requests to sensitive operations.
Potential Impact
For European organizations, this vulnerability poses a significant risk to the availability and confidentiality of web services built on Craft CMS. Resource exhaustion attacks can disrupt business-critical digital experiences, causing downtime and loss of customer trust. Information disclosure through unauthorized backups could expose sensitive customer data or internal configurations, leading to compliance violations under GDPR and other data protection regulations. Industries relying heavily on web content management and digital engagement platforms, such as e-commerce, media, and government services, may face operational and reputational damage. The ease of exploitation without authentication increases the threat surface, potentially allowing widespread automated attacks. Additionally, denial of service conditions could impact service level agreements and cause financial losses. The vulnerability's presence in multiple major versions means many organizations may be affected if they have not applied timely updates.
Mitigation Recommendations
1. Immediately upgrade Craft CMS installations to version 4.16.17, 5.8.21, or later to apply the official patches addressing this vulnerability. 2. Restrict access to administrative endpoints by implementing IP whitelisting or VPN-only access to reduce exposure to unauthenticated attackers. 3. Deploy web application firewalls (WAFs) with custom rules to detect and block unusual or excessive database backup requests. 4. Implement rate limiting on backup-related API endpoints to prevent resource exhaustion from repeated triggering. 5. Monitor logs for abnormal backup operation frequency or volume to detect potential exploitation attempts early. 6. Conduct regular security audits and vulnerability scans focusing on CMS components and their versions. 7. Educate development and operations teams about the risks of unauthenticated access to admin functions and enforce least privilege principles. 8. Consider isolating backup operations to separate infrastructure or sandbox environments to limit impact if exploited. 9. Review and tighten database access permissions to minimize data exposure in case of backup misuse.
Affected Countries
Germany, United Kingdom, France, Netherlands, Sweden, Belgium, Italy, Spain
CVE-2025-68456: CWE-770: Allocation of Resources Without Limits or Throttling in craftcms cms
Description
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.
AI-Powered Analysis
Technical Analysis
CVE-2025-68456 is a vulnerability classified under CWE-770 (Allocation of Resources Without Limits or Throttling) and CWE-202 (Information Exposure Through Data Query) affecting Craft CMS, a widely used platform for building digital experiences. The flaw exists in versions 3.0.0 through 4.16.16 and 5.0.0-RC1 through 5.8.20, where unauthenticated attackers can invoke database backup operations via specific administrative endpoints or actions. Because these operations are resource-intensive and lack proper throttling or limits, attackers can cause resource exhaustion, leading to denial of service conditions. Additionally, the backup process may expose sensitive information, resulting in potential data leakage. The vulnerability is remotely exploitable without requiring authentication or user interaction, increasing its risk profile. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), with high confidentiality and availability impacts (VC:H, VA:H), and partial temporal metrics (E:P). Although no exploits are currently known in the wild, the vulnerability's characteristics make it a credible threat. The recommended mitigation is to upgrade to patched versions 4.16.17 or 5.8.21 and later, which include fixes to enforce resource limits and prevent unauthorized backup triggering. Organizations still running vulnerable versions should implement compensating controls such as restricting access to admin endpoints, monitoring for unusual backup activity, and rate limiting requests to sensitive operations.
Potential Impact
For European organizations, this vulnerability poses a significant risk to the availability and confidentiality of web services built on Craft CMS. Resource exhaustion attacks can disrupt business-critical digital experiences, causing downtime and loss of customer trust. Information disclosure through unauthorized backups could expose sensitive customer data or internal configurations, leading to compliance violations under GDPR and other data protection regulations. Industries relying heavily on web content management and digital engagement platforms, such as e-commerce, media, and government services, may face operational and reputational damage. The ease of exploitation without authentication increases the threat surface, potentially allowing widespread automated attacks. Additionally, denial of service conditions could impact service level agreements and cause financial losses. The vulnerability's presence in multiple major versions means many organizations may be affected if they have not applied timely updates.
Mitigation Recommendations
1. Immediately upgrade Craft CMS installations to version 4.16.17, 5.8.21, or later to apply the official patches addressing this vulnerability. 2. Restrict access to administrative endpoints by implementing IP whitelisting or VPN-only access to reduce exposure to unauthenticated attackers. 3. Deploy web application firewalls (WAFs) with custom rules to detect and block unusual or excessive database backup requests. 4. Implement rate limiting on backup-related API endpoints to prevent resource exhaustion from repeated triggering. 5. Monitor logs for abnormal backup operation frequency or volume to detect potential exploitation attempts early. 6. Conduct regular security audits and vulnerability scans focusing on CMS components and their versions. 7. Educate development and operations teams about the risks of unauthenticated access to admin functions and enforce least privilege principles. 8. Consider isolating backup operations to separate infrastructure or sandbox environments to limit impact if exploited. 9. Review and tighten database access permissions to minimize data exposure in case of backup misuse.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-12-17T20:22:35.081Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 695c39ba3839e4417594b416
Added to database: 1/5/2026, 10:22:50 PM
Last enriched: 1/5/2026, 10:37:12 PM
Last updated: 1/8/2026, 11:34:48 AM
Views: 16
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-66001: CWE-295: Improper Certificate Validation in SUSE neuvector
HighCVE-2026-21874: CWE-772: Missing Release of Resource after Effective Lifetime in zauberzeug nicegui
MediumCVE-2026-21873: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in zauberzeug nicegui
HighCVE-2026-21872: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in zauberzeug nicegui
MediumCVE-2026-21871: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in zauberzeug nicegui
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.