CVE-2006-6378: BTSaveMySql 1.2 stores sensitive data under the web root with insufficient access control, which allows remote

This month

HIGH 7.5WATCHLISTDOWNGRADE

CVE-2006-6378 is a high-severity flaw (CVSS 7.5) affecting btsavemysql. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

BTSaveMySql 1.2 stores sensitive data under the web root with insufficient access control, which allows remote attackers to obtain configuration and save files via direct requests.

Why this priority

High severity
On your watchlist

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

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	1.5% (top 26%)
CISA exploited list	No
Published	2006-12-07
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: widcomm

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

Am I affected?

Timeline

2006-12-07 17:28 UTCPublished CVE record published
2026-06-16 22:32 UTCUpdated Record last modified

widcomm btsavemysql DOWNGRADE

Affected: 1.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.2

1. Check installed version

apt-cache policy btsavemysql || rpm -q btsavemysql || btsavemysql --version

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

apt-cache madison btsavemysql sudo apt install btsavemysql=<VERSION_BEFORE_1.2> sudo apt-mark hold btsavemysql

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

dnf --showduplicates list btsavemysql sudo dnf downgrade btsavemysql-<VERSION_BEFORE_1.2> sudo dnf versionlock add btsavemysql

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.

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-2006-6378?

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

Is CVE-2006-6378 being exploited?

CVE-2006-6378 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-2006-6378 affect?

CVE-2006-6378 affects btsavemysql. Severity is high (CVSS 7.5). BTSaveMySql 1.2 stores sensitive data under the web root with insufficient access control, which allows remote attackers to obtain configuration and save files via direct requests.

How urgent is CVE-2006-6378?

Priority 50/100. High severity; On your watchlist

References

← Back to latest CVEs