CVE-2014-1836 json
ImpressCMS Path Traversal to Arbitrary File Delete
published 2015-07-01 11 y ago modified 2026-06-17 4 mo ago also GHSA-wcj4-ff9m-5r7g , EUVD-2022-5555
- cvss
- 6.4
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.6%
- EPSS 3.6% chance of exploitation in 30 days, percentile 89%
- public exploits
- 1
- Exploit-DB
Summary
Absolute path traversal vulnerability in htdocs/libraries/image-editor/image-edit.php in ImpressCMS before 1.3.6 allows remote attackers to delete arbitrary files via a full pathname in the image_path parameter in a cancel action.
Patch / fix
- packagist impresscms/impresscms 1.3.6
Timeline
- First public exploit (EDB-31431)
- Published
Exploit prediction
3.64% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-31431 ImpressCMS 1.3.5 - Multiple Vulnerabilities webapps, 2014-02-05
- github.com https://github.com/pedrib/PoC/blob/master/generic/impresscms-1.3.5.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:N/I:P/A:P |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | impresscms/impresscms | <1.3.6 |
1.3.6 |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/pedrib/PoC/blob/master/generic/impresscms-1.3.5.txt
web, exploit
-
community.impresscms.org
/modules/smartsection/item.php?itemid=675
web, vendor-advisory
-
seclists.org
/fulldisclosure/2014/Feb/14
mailing-list, web
-
securityfocus.com
/bid/65279
vdb-entry
-
osvdb.org
/show/osvdb/102770
vdb-entry
-
nvd.nist.gov
/vuln/detail/CVE-2014-1836
advisory
-
github.com
/ImpressCMS/impresscms/issues/914
web
-
web.archive.org
/web/20200228234251/http://www.securityfocus.com/bid/65279
web
Sources
- CVE List CVE-2014-1836
- GitHub Advisory GHSA-wcj4-ff9m-5r7g
- NVD CVE-2014-1836
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.