How severe is CVE-2005-4768?

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

Is CVE-2005-4768 being actively exploited?

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

What products are affected by CVE-2005-4768?

CVE-2005-4768 primarily affects Tux Racer Tuxbank. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2005-4768?

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-4768 published?

CVE-2005-4768 was published on 2005-12-31 and last updated on 2026-06-16.

CVE-2005-4768

CVE-2005-4768 is a high-severity vulnerability in Tux Racer Tuxbank 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% (67th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Tux Racer Tuxbank
Published: 2005-12-31
Last modified: 2026-06-16

Description

SQL injection vulnerability in manage_account.php in Tux Racer TuxBank 0.7x and 0.8 allows remote attackers to execute arbitrary SQL commands via the id parameter in a manageaccount action to index.php.

Frequently asked questions

What is CVE-2005-4768?: SQL injection vulnerability in manage_account.php in Tux Racer TuxBank 0.7x and 0.8 allows remote attackers to execute arbitrary SQL commands via the id parameter in a manageaccount action to index.php.
How severe is CVE-2005-4768?: CVE-2005-4768 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2005-4768 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (67th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2005-4768?: CVE-2005-4768 primarily affects Tux Racer Tuxbank. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2005-4768?: 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-4768 published?: CVE-2005-4768 was published on 2005-12-31 and last updated on 2026-06-16.

References

Affected products (2)

cpe:2.3:a:tux_racer:tuxbank:0.7x:*:*:*:*:*:*:*
cpe:2.3:a:tux_racer:tuxbank:0.8:*:*:*:*:*:*:*

More vulnerabilities in Tux Racer Tuxbank

CVE-2005-4732 — Medium (CVSS 4.3): Multiple cross-site scripting (XSS) vulnerabilities in index.php in Tux Racer TuxBank 0.7x and 0.8 allow remote…

All CVEs affecting Tux Racer Tuxbank →