CVE-2005-0853: betaparticle blog (bp blog) stores the database under the web root, which allows remote attackers to obtain se

This month

MEDIUM 5.0DOWNGRADE

CVE-2005-0853 is a medium-severity flaw (CVSS 5.0) affecting betaparticle blog. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.0 (Medium)
EPSS exploit chance	3.5% (top 11%)
CISA exploited list	No
Published	2005-05-02
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: betaparticle

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2005-05-02 04:00 UTCPublished CVE record published
2026-06-16 22:11 UTCUpdated Record last modified

betaparticle betaparticle blog DOWNGRADE

Affected: 2.0 · 3.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.0

1. Check installed version

apt-cache policy betaparticle-blog || rpm -q betaparticle-blog || betaparticle-blog --version

2. No fixed release: DOWNGRADE to a release before 2.0 (Debian / Ubuntu)

apt-cache madison betaparticle-blog sudo apt install betaparticle-blog=<VERSION_BEFORE_2.0> sudo apt-mark hold betaparticle-blog

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list betaparticle-blog sudo dnf downgrade betaparticle-blog-<VERSION_BEFORE_2.0> sudo dnf versionlock add betaparticle-blog

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: BetaParticle blog 2.0/3.0 - dbBlogMX.mdb Direct Request Database Disclosure

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2005-0853?

betaparticle blog: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2005-0853 being exploited?

CVE-2005-0853 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2005-0853 affect?

CVE-2005-0853 affects betaparticle blog. Severity is medium (CVSS 5.0). 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.

How urgent is CVE-2005-0853?

Priority 45/100. Public exploit reference

Related CVEs

CVE-2007-1445 HIGH 7.5 UPGRADE SQL injection vulnerability in the heme preview feature for default.asp in BP Blog 7.0 through 7.0.2 allows re
CVE-2006-1333 MEDIUM 6.4 DOWNGRADE Multiple SQL injection vulnerabilities in BetaParticle Blog 6.0 and earlier allow remote attackers to execute
CVE-2005-0854 HIGH 7.5 DOWNGRADE betaparticle blog (bp blog), posisbly before version 4, allows remote attackers to bypass authentication and (

References

← Back to latest CVEs