Menu

Star on GitHub · 3.2k

CVE-2012-6519

7.5 · HIGH

SQL injection vulnerability in modules/poll/index.php in DIY-CMS 1.0 allows remote attackers to execute arbitrary SQL commands via the start parameter to mod.php.

Published Jan 24, 2013diy-cmsCWE-89EPSS 1.71%

Overview

CVE-2012-6519 is a high-severity vulnerability affecting diy-cms diy-cms. It was published on January 24, 2013 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 modules/poll/index.php in DIY-CMS 1.0 allows remote attackers to execute arbitrary SQL commands via the start parameter to mod.php.

Remediation

Check the references section for vendor advisories and patches from diy-cms. Update diy-cms 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-2012-6519?

CVE-2012-6519 is a high-severity vulnerability affecting diy-cms diy-cms. It was published on January 24, 2013 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2012-6519?

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-2012-6519?

Check the references section for vendor advisories and patches from diy-cms. Update diy-cms 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-2012-6519?

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

View all