CVE-2009-4465 json
DeluxeBB 1.3 stores sensitive information under the web root with insufficient access control, which allows remote attackers to obtain user…
published 16y ago modified 4mo ago also EUVD-2009-4432
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 83%
- public exploits
- 1
- Exploit-DB
Summary
DeluxeBB 1.3 stores sensitive information under the web root with insufficient access control, which allows remote attackers to obtain user and configuration information, log data, and gain administrative access via a direct request to scripts in (1) templates/ including (2) templates/deluxe/admincp/, (3) templates/corporate/admincp/, and (4) templates/blue/admincp/; (5) images/; (6) logs/ including (7) logs/cp.php; (8) wysiwyg/; (9) docs/; (10) classes/; (11) lang/; and (12) settings/.
Is CVE-2009-4465 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-10598)
- Published
Exploit prediction
2.37% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-10598 DeluxeBB 1.3 - Multiple Vulnerabilities webapps, 2009-12-22
- securityfocus.com http://www.securityfocus.com/bid/37448 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/10598
exploit
-
securityfocus.com
/bid/37448
vdb-entry, exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/54975
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/54977
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/54978
vdb-entry
Sources
- CVE List CVE-2009-4465
- NVD CVE-2009-4465
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.