LiveActive security incident?Get immediate response
CVE Record

CVE-2006-6966: phpGraphy before 0.9.13a does not properly unset variables when the input data includes a numeric parameter...

phpGraphy before 0.9.13a does not properly unset variables when the input data includes a numeric parameter with a value matching an alphanumeric parameter's hash value, which allows remote attackers to execute arbitrary PHP code by uploading a config.php file via the pictures[] parameter to index.php. NOTE: it could be argued that this vulnerability is due to a bug in the unset PHP command (CVE-2006-3017) and the proper fix should be in PHP; if so, then this should not be treated as a vulnerability in phpGraphy.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2006-6966 is an old phpGraphy issue that could let a remote attacker make the application run attacker-supplied PHP. The business risk is highest where legacy phpGraphy instances are still internet-facing, especially with upload features enabled. The supplied sources do not show current active exploitation. Exposure is most likely limited to legacy phpGraphy deployments older than 0.9.13a. Internet-facing galleries, upload-capable deployments, and forgotten SourceForge-era PHP applications deserve priority review. The source bundle does not provide CPEs or a complete affected-version inventory. Prioritize this if phpGraphy exists in exposed or legacy environments. The issue is old, but the impact is serious because successful exploitation could lead to server-side code execution. If phpGraphy is not present, no further action is needed beyond documenting that finding. Mitigation focus: Identify whether phpGraphy is deployed anywhere in production or archives.; Upgrade phpGraphy to 0.9.13a or later where still used.; Remove or isolate abandoned phpGraphy deployments if upgrade is impractical..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2006-6966 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.