How severe is CVE-2014-1836?

No CVSS score has been assigned to CVE-2014-1836 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-1836?

CVE-2014-1836 affects the following packages: impresscms/impresscms (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2014-1836?

Update impresscms/impresscms to 1.3.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-1836 is resolved across your whole dependency graph.

How do I detect CVE-2014-1836 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for impresscms/impresscms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2014-1836 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2014-1836 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2014-1836, including 1 documented proof-of-concept exploit on Exploit-DB and 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2014-1836?

CVE-2014-1836 has an EPSS (Exploit Prediction Scoring System) score of 3.6%, placing it in the 90th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2014-1836?

CVE-2014-1836 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2014-1836 published, and has it been updated?

CVE-2014-1836 was published on May 17, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2014-1836 — impresscms

CVE-2014-1836 is a Path Traversal vulnerability in impresscms/impresscms. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for impresscms/impresscms — see the affected versions and patch details below.

ImpressCMS Path Traversal to Arbitrary File Delete

Published

May 17, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

3.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐘impresscms/impresscms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`impresscms/impresscms`	all versions	1.3.6`composer require impresscms/impresscms:^1.3.6`

Affected Products

1 product · 1 configurations

Application

impresscmsimpresscms

≤ 1.3.5

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-31431webappsphp✓ Verified

ImpressCMS 1.3.5 - Multiple Vulnerabilities

by Pedro Ribeiro · Feb 5, 2014

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for impresscms/impresscms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update impresscms/impresscms to 1.3.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-1836 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2014-1836 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works