How severe is CVE-2006-3013?

CVE-2006-3013 has a CVSS 2.0 base score of 5.1, rated medium severity.

Is CVE-2006-3013 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (79th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2006-3013?

CVE-2006-3013 primarily affects Eschew.net Phpbannerexchange. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2006-3013?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2006-3013 published?

CVE-2006-3013 was published on 2006-06-19 and last updated on 2026-06-16.

CVE-2006-3013

CVE-2006-3013 is a medium-severity vulnerability in Eschew.net Phpbannerexchange with a CVSS 2.0 base score of 5.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 2.0 base score 5.1)
EPSS exploit prediction: 2% (79th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Eschew.net Phpbannerexchange
Published: 2006-06-19
Last modified: 2026-06-16

Description

Interpretation conflict in resetpw.php in phpBannerExchange before 2.0 Update 6 allows remote attackers to execute arbitrary SQL commands via an email parameter containing a null (%00) character after a valid e-mail address, which passes the validation check in the eregi PHP command. NOTE: it could be argued that this vulnerability is due to a bug in the eregi PHP command and the proper fix should be in PHP; if so, then this should not be treated as a vulnerability in phpBannerExchange.

Frequently asked questions

What is CVE-2006-3013?: Interpretation conflict in resetpw.php in phpBannerExchange before 2.0 Update 6 allows remote attackers to execute arbitrary SQL commands via an email parameter containing a null (%00) character after a valid e-mail address, which passes the validation check in the eregi PHP command. NOTE: it could be argued that this vulnerability is due to a bug in the eregi PHP command and the proper fix should be in PHP; if so, then this should not be treated as a vulnerability in phpBannerExchange.
How severe is CVE-2006-3013?: CVE-2006-3013 has a CVSS 2.0 base score of 5.1, rated medium severity.
Is CVE-2006-3013 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (79th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2006-3013?: CVE-2006-3013 primarily affects Eschew.net Phpbannerexchange. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2006-3013?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2006-3013 published?: CVE-2006-3013 was published on 2006-06-19 and last updated on 2026-06-16.

References

Affected products (6)

cpe:2.3:a:eschew.net:phpbannerexchange:2.0:*:*:*:*:*:*:*
cpe:2.3:a:eschew.net:phpbannerexchange:2.0_update_1:*:*:*:*:*:*:*
cpe:2.3:a:eschew.net:phpbannerexchange:2.0_update_2:*:*:*:*:*:*:*
cpe:2.3:a:eschew.net:phpbannerexchange:2.0_update_3:*:*:*:*:*:*:*
cpe:2.3:a:eschew.net:phpbannerexchange:2.0_update_4:*:*:*:*:*:*:*
cpe:2.3:a:eschew.net:phpbannerexchange:2.0_update_5:*:*:*:*:*:*:*

More vulnerabilities in Eschew.net Phpbannerexchange

CVE-2006-3012 — High (CVSS 7.5): SQL injection vulnerability in phpBannerExchange before 2.0 Update 6 allows remote attackers to execute arbitrary SQL…
CVE-2006-1201 — Medium (CVSS 5.0): Directory traversal vulnerability in resetpw.php in eschew.net phpBannerExchange 2.0 and earlier, and other versions…

All CVEs affecting Eschew.net Phpbannerexchange →