CVE-2008-7209 json
Unrestricted file upload vulnerability in the add2 action in a_upload.php in OneCMS 2.4, and possibly earlier, allows remote attackers to e…
published 2009-09-11 17 y ago modified 2026-06-16 4 mo ago also EUVD-2008-7168
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.0%
- EPSS 6.0% chance of exploitation in 30 days, percentile 93%
- public exploits
- 1
- Exploit-DB
Summary
Unrestricted file upload vulnerability in the add2 action in a_upload.php in OneCMS 2.4, and possibly earlier, allows remote attackers to execute arbitrary code by uploading a file with an executable extension and using a safe content type such as image/gif, then accessing it via a direct request to the file in an unspecified directory.
Timeline
- First public exploit (EDB-4857)
- Published
Exploit prediction
6.01% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-4857 OneCMS 2.4 - SQL Injection / Upload webapps, 2008-01-07
- bugreport.ir http://www.bugreport.ir/index_26.htm referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/27158 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-264 Permissions, Privileges, and Access Controls
References
-
exploit-db.com
/exploits/4857
exploit
-
bugreport.ir
/index_26.htm
exploit
-
securityfocus.com
/bid/27158
vdb-entry, exploit
-
vupen.com
/english/advisories/2008/0081
vdb-entry, vendor-advisory
-
securityfocus.com
/archive/1/485837/100/200/threaded
mailing-list
- sourceforge.net /forum/forum.php?forum_id=774946
-
securityfocus.com
/archive/1/487136/100/200/threaded
mailing-list
-
osvdb.org
/51117
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/39485
vdb-entry
Sources
- CVE List CVE-2008-7209
- NVD CVE-2008-7209
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.