Menu

Star on GitHub · 3.2k

CVE-2008-0253

7.5 · HIGH

SQL injection vulnerability in full_text.php in Binn SBuilder allows remote attackers to execute arbitrary SQL commands via the nid parameter.

Published Jan 15, 2008binnCWE-89EPSS 0.97%

Overview

CVE-2008-0253 is a high-severity vulnerability affecting binn sbuilder. It was published on January 15, 2008 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 full_text.php in Binn SBuilder allows remote attackers to execute arbitrary SQL commands via the nid parameter.

Remediation

Check the references section for vendor advisories and patches from binn. Update sbuilder 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-2008-0253?

CVE-2008-0253 is a high-severity vulnerability affecting binn sbuilder. It was published on January 15, 2008 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2008-0253?

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-2008-0253?

Check the references section for vendor advisories and patches from binn. Update sbuilder 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-2008-0253?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2008-0253 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 2008

View all