CVE-2006-3012: SQL injection vulnerability in phpBannerExchange before 2.0 Update 6 allows remote attackers to execute arbitr

This month

HIGH 7.5DOWNGRADE

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

SQL injection vulnerability in phpBannerExchange before 2.0 Update 6 allows remote attackers to execute arbitrary SQL commands via the (1) login parameter in (a) client/stats.php and (b) admin/stats.php, or the (2) pass parameter in client/stats.php.

Why this priority

High severity
Public exploit reference

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

Risk facts

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

Publisher (CNA): MITRE · Vendor: eschew.net

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

Am I affected?

Timeline

2006-06-19 10:02 UTCPublished CVE record published
2026-06-16 22:26 UTCUpdated Record last modified

eschew.net phpbannerexchange DOWNGRADE

Affected: 2.0 · 2.0_update_1 · 2.0_update_2 · 2.0_update_3 · 2.0_update_4 · 2.0_update_5

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.0

1. Check installed version

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

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

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

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

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

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-3012?

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

Is CVE-2006-3012 being exploited?

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

CVE-2006-3012 affects phpbannerexchange. Severity is high (CVSS 7.5). SQL injection vulnerability in phpBannerExchange before 2.0 Update 6 allows remote attackers to execute arbitrary SQL commands via the (1) login parameter in (a) client/stats.php and (b) admin/stats.php, or the (2) pass parameter in client/

How urgent is CVE-2006-3012?

Priority 50/100. High severity; Public exploit reference

Software pages

PHP vulnerabilities

Related CVEs

CVE-2010-2258 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in signupconfirm.php in phpBannerExchange 1.2 Arabic allows remote at
CVE-2006-3013 MEDIUM 5.1 DOWNGRADE Interpretation conflict in resetpw.php in phpBannerExchange before 2.0 Update 6 allows remote attackers to exe
CVE-2006-1201 MEDIUM 5.0 DOWNGRADE Directory traversal vulnerability in resetpw.php in eschew.net phpBannerExchange 2.0 and earlier, and other ve

References

← Back to latest CVEs