Miggo at BlackHat 2026!
Easily map the attack path and prioritize which CVEs are a threat to your organization
Miggo AIGenerate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance
| Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
|---|---|---|---|
| concrete5/concrete5 | composer | < 9.5.1 | 9.5.1 |
Miggo AIRoot Cause AnalysisThe vulnerability description specifies an 'Inverted CSRF token check in the DeleteFile controller'. To identify the vulnerable function, I analyzed the commits between the last vulnerable version (9.5.0) and the patched version (9.5.1). This led me to the security patch commit f22b9dff59454391a50a255a39995bf635deea9e. Within this commit, the changes in the file concrete/controllers/frontend/conversations/delete_file.php directly address the described vulnerability. The view function in the DeleteFile controller had its CSRF token validation logic corrected from if ($token->validate(...)) to if (!$token->validate(...)). The original, flawed logic would only raise an error for valid tokens, thereby disabling CSRF protection for the file deletion action. This allowed an attacker to craft a malicious request that, when triggered by a privileged user, would result in unauthorized file deletion. Therefore, the identified vulnerable function is Concrete\Controller\Frontend\Conversations\DeleteFile::view.
