How severe is CVE-2005-4240?

CVE-2005-4240 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2005-4240 being actively exploited?

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

What products are affected by CVE-2005-4240?

CVE-2005-4240 primarily affects Vcd-db. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2005-4240?

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-2005-4240 published?

CVE-2005-4240 was published on 2005-12-14 and last updated on 2026-06-16.

CVE-2005-4240

CVE-2005-4240 is a high-severity vulnerability in Vcd-db 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: 1% (63rd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Vcd-db
Published: 2005-12-14
Last modified: 2026-06-16

Description

SQL injection vulnerability in search.php in VCD-db 0.98 and earlier allows remote attackers to execute arbitrary SQL commands via the by parameter.

Frequently asked questions

What is CVE-2005-4240?: SQL injection vulnerability in search.php in VCD-db 0.98 and earlier allows remote attackers to execute arbitrary SQL commands via the by parameter.
How severe is CVE-2005-4240?: CVE-2005-4240 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2005-4240 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (63rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2005-4240?: CVE-2005-4240 primarily affects Vcd-db. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2005-4240?: 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-2005-4240 published?: CVE-2005-4240 was published on 2005-12-14 and last updated on 2026-06-16.

References

Affected products (6)

cpe:2.3:a:vcd-db:vcd-db:0.97:*:*:*:*:*:*:*
cpe:2.3:a:vcd-db:vcd-db:0.98:*:*:*:*:*:*:*
cpe:2.3:a:vcd-db:vcd-db:0.961:*:*:*:*:*:*:*
cpe:2.3:a:vcd-db:vcd-db:0.971:*:*:*:*:*:*:*
cpe:2.3:a:vcd-db:vcd-db:0.972:*:*:*:*:*:*:*
cpe:2.3:a:vcd-db:vcd-db:0.973:*:*:*:*:*:*:*

More vulnerabilities in Vcd-db

CVE-2006-4628 — Medium (CVSS 4.3): Cross-site scripting (XSS) vulnerability in VCD-db before 0.983 allows remote attackers to inject arbitrary web script…
CVE-2005-4241 — Medium (CVSS 4.3): Cross-site scripting (XSS) vulnerability in the category page in VCD-db 0.98 and earlier allows remote attackers to…

All CVEs affecting Vcd-db →