Menu

Star on GitHub · 3.2k

CVE-2009-3659

7.5 · HIGH

SQL injection vulnerability in file/stats.php in BS Counter 2.5.3 allows remote attackers to execute arbitrary SQL commands via the page parameter.

Published Oct 11, 2009stanbackCWE-89EPSS 0.93%

Overview

CVE-2009-3659 is a high-severity vulnerability affecting stanback bs_counter. It was published on October 11, 2009 and has a CVSS 2.0 base score of 7.5 (HIGH).

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

SQL injection vulnerability in file/stats.php in BS Counter 2.5.3 allows remote attackers to execute arbitrary SQL commands via the page parameter.

Remediation

Check the references section for vendor advisories and patches from stanback. Update bs_counter to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2009-3659?

CVE-2009-3659 is a high-severity vulnerability affecting stanback bs_counter. It was published on October 11, 2009 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2009-3659?

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2009-3659?

Check the references section for vendor advisories and patches from stanback. Update bs_counter to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2009-3659?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2009-3659 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2009

View all