Menu

Star on GitHub · 3.2k

CVE-2007-2167

7.5 · HIGH

Static code injection vulnerability in process.php in AimStats 3.2 allows remote attackers to inject PHP code into config.php via the number parameter in an update action.

Published Apr 22, 2007aimstatsEPSS 44.43%

Overview

CVE-2007-2167 is a high-severity vulnerability affecting aimstats aimstats. It was published on April 22, 2007 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

Static code injection vulnerability in process.php in AimStats 3.2 allows remote attackers to inject PHP code into config.php via the number parameter in an update action.

Remediation

Check the references section for vendor advisories and patches from aimstats. Update aimstats 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-2007-2167?

CVE-2007-2167 is a high-severity vulnerability affecting aimstats aimstats. It was published on April 22, 2007 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2007-2167?

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-2007-2167?

Check the references section for vendor advisories and patches from aimstats. Update aimstats 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-2007-2167?

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

View all