How severe is CVE-2006-3572?

CVE-2006-3572 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2006-3572 being actively exploited?

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

What products are affected by CVE-2006-3572?

CVE-2006-3572 primarily affects Papoo. 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-3572?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2006-3572 published?

CVE-2006-3572 was published on 2006-07-13 and last updated on 2026-06-16.

CVE-2006-3572

CVE-2006-3572 is a high-severity vulnerability in Papoo with a CVSS 2.0 base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 2.0 base score 7.5)
EPSS exploit prediction: 2% (78th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Papoo
Published: 2006-07-13
Last modified: 2026-06-16

Description

SQL injection vulnerability in forumthread.php in Papoo 3 RC3 and earlier allows remote attackers to execute arbitrary SQL commands via the msgid parameter.

Frequently asked questions

What is CVE-2006-3572?: SQL injection vulnerability in forumthread.php in Papoo 3 RC3 and earlier allows remote attackers to execute arbitrary SQL commands via the msgid parameter.
How severe is CVE-2006-3572?: CVE-2006-3572 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2006-3572 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (78th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2006-3572?: CVE-2006-3572 primarily affects Papoo. 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-3572?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2006-3572 published?: CVE-2006-3572 was published on 2006-07-13 and last updated on 2026-06-16.

References

Affected products (6)

cpe:2.3:a:papoo:papoo:*:*:*:*:*:*:*:*
cpe:2.3:a:papoo:papoo:2.1.2:*:*:*:*:*:*:*
cpe:2.3:a:papoo:papoo:2.1.4:*:*:*:*:*:*:*
cpe:2.3:a:papoo:papoo:2.1.5:*:*:*:*:*:*:*
cpe:2.3:a:papoo:papoo:3.0.0:*:*:*:*:*:*:*
cpe:2.3:a:papoo:papoo:3.0.0_beta1:*:*:*:*:*:*:*

More vulnerabilities in Papoo

CVE-2021-29054 — High (CVSS 8.8): Certain Papoo products are affected by: Cross Site Request Forgery (CSRF) in the admin interface. This affects Papoo…
CVE-2008-3724 — High (CVSS 7.5): SQL injection vulnerability in index.php in Papoo before 3.7.2 allows remote attackers to execute arbitrary SQL…
CVE-2007-3453 — High (CVSS 7.5): SQL injection vulnerability in Papoo 3.6, and possibly earlier, allows remote attackers to execute arbitrary SQL…
CVE-2007-2320 — High (CVSS 7.5): SQL injection vulnerability in kontakt.php in Papoo 3.02 and earlier allows remote attackers to execute arbitrary SQL…
CVE-2005-4478 — High (CVSS 7.5): Multiple SQL injection vulnerabilities in Papoo 2.1.2 and earlier allow remote attackers to execute arbitrary SQL…
CVE-2007-3494 — Medium (CVSS 6.8): Papoo CMS 3.6, and possibly earlier, does not verify user privileges when accessing the backend administration plugins,…

All CVEs affecting Papoo →