CVE-2009-4098 json
Unrestricted file upload vulnerability in banner-edit.php in OpenX adserver 2.8.1 and earlier allows remote authenticated users with banner…
published 2009-11-28 16 y ago modified 2026-06-16 4 mo ago also EUVD-2009-4069
- cvss
- 6.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 18.7%
- EPSS 18.7% chance of exploitation in 30 days, percentile 97%
- public exploits
- 2
- Metasploit, Exploit-DB
Summary
Unrestricted file upload vulnerability in banner-edit.php in OpenX adserver 2.8.1 and earlier allows remote authenticated users with banner / file upload permissions to execute arbitrary code by uploading a file with an executable extension, then accessing it via a direct request to the file in an images directory.
Timeline
- First public exploit (Metasploit exploit/unix/webapp/openx_banner_edit)
- Published
Exploit prediction
18.68% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit exploit/unix/webapp/openx_banner_edit OpenX banner-edit.php File Upload PHP Code Execution metasploit exploit, excellent rank, 2009-11-24
- EDB-16903 OpenX - 'banner-edit.php' Arbitrary File Upload / PHP Code Execution (Metasploit) remote, 2010-09-20
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.0 | AV:N/AC:M/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
openx.org
/docs/2.8/release-notes/openx-2.8.2
vendor-advisory
-
secunia.com
/advisories/37475
third-party-advisory, vendor-advisory
-
securityfocus.com
/archive/1/508050/100/0/threaded
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/54394
vdb-entry
- developer.openx.org /jira/browse/OX-5747
-
securityfocus.com
/bid/37110
vdb-entry
-
osvdb.org
/60499
vdb-entry
Sources
- CVE List CVE-2009-4098
- NVD CVE-2009-4098
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.