CVE-2005-0853 json
betaparticle blog (bp blog) stores the database under the web root, which allows remote attackers to obtain sensitive information via a dir…
published 2005-03-24 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-0854
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.5%
- EPSS 3.5% chance of exploitation in 30 days, percentile 89%
- public exploits
- 1
- Exploit-DB
Summary
betaparticle blog (bp blog) stores the database under the web root, which allows remote attackers to obtain sensitive information via a direct request to (1) dbBlogMX.mdb for versions before 3.0, or (2) Blog.mdb for versions 3.0 and later. NOTE: it was later reported that vector 2 also affects versions 6.0 through 9.0.
Patch / fix
- secunia.com/advisories/14668 advisory
Timeline
- First public exploit (EDB-25252)
- Published
Exploit prediction
3.52% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-25252 BetaParticle blog 2.0/3.0 - dbBlogMX.mdb Direct Request Database Disclosure webapps, 2005-03-21
- exploit-db.com https://www.exploit-db.com/exploits/7499 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/12861 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
References
-
secunia.com
/advisories/14668
third-party-advisory, patch, vendor-advisory
-
exploit-db.com
/exploits/7499
exploit
-
securityfocus.com
/bid/12861
vdb-entry, exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/47419
vdb-entry
-
seclists.org
/lists/bugtraq/2005/Mar/0360.html
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/19779
vdb-entry
-
secunia.com
/advisories/33233
third-party-advisory
Sources
- CVE List CVE-2005-0853
- NVD CVE-2005-0853
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.