CVE-2008-6178 json
Unrestricted file upload vulnerability in editor/filemanager/browser/default/connectors/php/connector.php in FCKeditor 2.2, as used in Falt…
published 2009-02-19 17 y ago modified 2026-06-16 4 mo ago also EUVD-2008-6148
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.8%
- EPSS 7.8% chance of exploitation in 30 days, percentile 94%
- public exploits
- 2
- Exploit-DB
Summary
Unrestricted file upload vulnerability in editor/filemanager/browser/default/connectors/php/connector.php in FCKeditor 2.2, as used in Falt4 CMS, Nuke ET, and other products, allows remote attackers to execute arbitrary code by creating a file with PHP sequences preceded by a ZIP header, uploading this file via a FileUpload action with the application/zip content type, and then accessing this file via a direct request to the file in UserFiles/File/, probably a related issue to CVE-2005-4094. NOTE: some of these details are obtained from third party information.
Timeline
- First public exploit (EDB-6783)
- Published
Exploit prediction
7.81% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-8060 Falt4 CMS RC4 - 'FCKeditor' Arbitrary File Upload webapps, 2009-02-16
- EDB-6783 Nuke ET 3.4 - 'FCKeditor' Arbitrary File Upload webapps, 2008-10-18
- securityfocus.com http://www.securityfocus.com/bid/31812 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
exploit-db.com
/exploits/8060
exploit
-
securityfocus.com
/bid/31812
vdb-entry, exploit
-
secunia.com
/advisories/33973
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2009/0447
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/48769
vdb-entry
Sources
- CVE List CVE-2008-6178
- NVD CVE-2008-6178
Fencer Vulns 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.