A Remote Code Execution vulnerability has been found in the Horde_Image library when using the "Im" backend that utilizes ImageMagick's "convert" utility. It's not exploitable through any Horde application, because the code path to the vulnerability is not used by any Horde code. Custom applications using the Horde_Image library might be affected. This vulnerability affects all versions of Horde_Image from 2.0.0 to 2.5.1, and is fixed in 2.5.2. The problem is missing input validation of the index field in _raw() during construction of an ImageMagick command line.
This vulnerability carries a HIGH severity rating with a CVSS v3.1 score of 8.1, indicating it can be exploited remotely over the network but requires specific conditions to be met without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts confidentiality (data exposure), integrity (unauthorized modifications), and availability (service disruption) for affected systems. Impacting 1 product from horde organizations running these solutions should prioritize assessment and patching.
First disclosed in 2017, this vulnerability was reported during a period defined by widespread IoT adoption challenges, mobile security concerns, and the emergence of advanced persistent threat (APT) techniques. Contemporary mitigation strategies focused on secure development practices and third-party component vetting.
2017-09-21T17:29:00.590
2026-06-17T01:06:33.907
Modified
CVSSv3.0: 8.1 (HIGH)
AV:N/AC:M/Au:N/C:P/I:P/A:P
8.6
6.4
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | horde | horde_image_api | 2.0.0 | Yes |
| Application | horde | horde_image_api | 2.0.0 | Yes |
| Application | horde | horde_image_api | 2.0.0 | Yes |
| Application | horde | horde_image_api | 2.0.0 | Yes |
| Application | horde | horde_image_api | 2.0.1 | Yes |
| Application | horde | horde_image_api | 2.0.2 | Yes |
| Application | horde | horde_image_api | 2.0.3 | Yes |
| Application | horde | horde_image_api | 2.0.4 | Yes |
| Application | horde | horde_image_api | 2.0.5 | Yes |
| Application | horde | horde_image_api | 2.0.6 | Yes |
| Application | horde | horde_image_api | 2.0.7 | Yes |
| Application | horde | horde_image_api | 2.0.8 | Yes |
| Application | horde | horde_image_api | 2.0.9 | Yes |
| Application | horde | horde_image_api | 2.1.0 | Yes |
| Application | horde | horde_image_api | 2.2.0 | Yes |
| Application | horde | horde_image_api | 2.3.0 | Yes |
| Application | horde | horde_image_api | 2.3.1 | Yes |
| Application | horde | horde_image_api | 2.3.2 | Yes |
| Application | horde | horde_image_api | 2.3.3 | Yes |
| Application | horde | horde_image_api | 2.3.4 | Yes |
| Application | horde | horde_image_api | 2.3.5 | Yes |
| Application | horde | horde_image_api | 2.3.6 | Yes |
| Application | horde | horde_image_api | 2.4.0 | Yes |
| Application | horde | horde_image_api | 2.4.1 | Yes |
| Application | horde | horde_image_api | 2.5.0 | Yes |
| Application | horde | horde_image_api | 2.5.1 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For horde's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.