Goal Reached Thanks to every supporter β€” we hit 100%!

Goal: 1000 CNY Β· Raised: 1000 CNY

100.0%

CVE-2025-32432 β€” AI Deep Analysis Summary

CVSS 10.0 Β· Critical

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: CraftCMS suffers from a critical Remote Code Execution (RCE) vulnerability via insecure deserialization.…

Q2Root Cause? (CWE/Flaw)

πŸ›‘οΈ **Root Cause**: CWE-94 (Code Injection) / Insecure Deserialization.…

Q3Who is affected? (Versions/Components)

πŸ“¦ **Affected Versions**: β€’ **Craft CMS 3.x**: 3.0.0-RC1 to 3.9.14 β€’ **Craft CMS 4.x**: 4.0.0-RC1 to 4.14.14 β€’ **Craft CMS 5.x**: 5.0.0-RC1 to 5.6.16 ⚠️ *All versions prior to the fixed releases are at risk.*

Q4What can hackers do? (Privileges/Data)

πŸ”“ **Attacker Capabilities**: β€’ **Full RCE**: Execute system commands remotely. β€’ **Data Access**: Read/Write sensitive files and database contents. β€’ **Privilege Escalation**: Gain administrative control over the CMS an…

Q5Is exploitation threshold high? (Auth/Config)

⚑ **Exploitation Threshold**: **LOW**. β€’ **Authentication**: **None required** (Pre-auth). β€’ **Requirements**: Only a valid **Asset ID** is needed. β€’ **Complexity**: Low complexity attack vector with high impact.

Q6Is there a public Exp? (PoC/Wild Exploitation)

πŸ” **Public Exploits**: **YES**. β€’ Multiple PoCs available on GitHub (e.g., `Chocapikk`, `Sachinart`, `CTY-Research-1`). β€’ Automated scanners like **Nuclei** have templates ready. β€’ Wild exploitation is highly likely due…

Q7How to self-check? (Features/Scanning)

πŸ”Ž **Self-Check Methods**: β€’ Use **Nuclei** templates for CVE-2025-32432. β€’ Run specialized checkers like `Blackash-CVE-2025-32432` or Python PoCs. β€’ Scan for vulnerable asset transform endpoints. β€’ Check version numbers…

Q8Is it fixed officially? (Patch/Mitigation)

βœ… **Official Fix**: **YES**. β€’ **Craft CMS 3.9.15** β€’ **Craft CMS 4.14.15** β€’ **Craft CMS 5.6.17** πŸ“… **Release Date**: April 10, 2025. Update immediately to these versions.

Q9What if no patch? (Workaround)

🚧 **No Patch Workaround**: β€’ **Isolate** the asset transform functionality. β€’ **Restrict** access to asset IDs via WAF rules. β€’ **Monitor** logs for suspicious deserialization attempts. β€’ **Disable** unnecessary asset p…

Q10Is it urgent? (Priority Suggestion)

πŸ”₯ **Urgency**: **CRITICAL (Priority 1)**. β€’ CVSS Score: **10.0** (Critical). β€’ Pre-auth RCE means immediate threat. β€’ Public exploits are available. β€’ **Action**: Patch NOW or isolate the system immediately.