Quick answers
- Is CVE-2026-16219 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16219 being exploited in the wild.
- How severe is CVE-2026-16219?
- Medium severity, with a CVSS score of 6.3, published 19 July 2026.
- Which products and versions are affected?
- Croogo Up to 4.0.7.
- Is there a fix for CVE-2026-16219?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-16219 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-16219?
- Check whether you run Croogo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability exists in Croogo CMS up to version 4.0.7 within the Admin File Manager component. The root cause is located in `FileManager::isEditable` in `FileManager/src/Utility/FileManager.php`, which incorrectly uses `Configure::check()` instead of `Configure::read()`. This results in a boolean value being used for path validation instead of the actual allowed directory list, effectively failing to enforce directory boundaries. An authenticated attacker with access to the File Manager can exploit this via remote network requests to create or overwrite files outside of the intended `WWW_ROOT/assets` directory. If the attacker writes a PHP file to a web-accessible directory, this can lead to remote code execution (RCE). Exploitation requires a valid session and a CSRF token.
Affected products
- Croogo CMS Up to 4.0.7
Timeline
- 2026-06-13: disclosed: Issue reported to vendor via GitHub
- 2026-07-19: advisory: CVE published via VulDB/NVD