Menu

Star on GitHub · 3.2k

CVE-2015-2066

7.5 · HIGH

SQL injection vulnerability in DLGuard 4.5 allows remote attackers to execute arbitrary SQL commands via the c parameter to index.php.

Published Feb 24, 2015dlguardCWE-89EPSS 1.26%

Overview

CVE-2015-2066 is a high-severity vulnerability affecting dlguard dlguard. It was published on February 24, 2015 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 DLGuard 4.5 allows remote attackers to execute arbitrary SQL commands via the c parameter to index.php.

Remediation

Check the references section for vendor advisories and patches from dlguard. Update dlguard 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-2015-2066?

CVE-2015-2066 is a high-severity vulnerability affecting dlguard dlguard. It was published on February 24, 2015 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2015-2066?

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-2015-2066?

Check the references section for vendor advisories and patches from dlguard. Update dlguard 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-2015-2066?

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

View all