Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2008-6851: SQL Injection in PHP Link Directory 3.3 (page.php)

Published Jul 7, 2009 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.1Medium · v2
EPSS0.88%60th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Php Link Directory
IdentifiersCVE-2008-6851CWE-89 · Improper Neutralization of Special…

A SQL injection vulnerability exists in PHP Link Directory (phpLD) 3.3, specifically in page.php. The vulnerability is present when the PHP configuration has register_globals enabled and magic_quotes_gpc disabled. An attacker can exploit the 'name' parameter to inject arbitrary SQL commands, potentially compromising the application's database.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to execute arbitrary SQL commands against the application's database, which can lead to data leakage, data modification, or complete compromise of the application's backend.

Mitigation

If you can’t patch tonight, do this now.

Disable register_globals and enable magic_quotes_gpc in the PHP configuration as a temporary mitigation. Employ web application firewalls and input validation to reduce the risk of exploitation.

Remediation

Patch, then assume compromise.

Upgrade to a version of phpLD that properly sanitizes user input and is not vulnerable to SQL injection. Additionally, ensure that register_globals is disabled and input is properly escaped or parameterized in SQL queries.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Php Link DirectoryPhp Link Directoryapplication
FAQ

Frequently asked questions

Is CVE-2008-6851 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2008-6851 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2008-6851?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2008-6851.
Is there a patch for CVE-2008-6851?
Upgrade to a version of phpLD that properly sanitizes user input and is not vulnerable to SQL injection. Additionally, ensure that register_globals is disabled and input is properly escaped or parameterized in SQL queries.
What products are affected by CVE-2008-6851?
Php Link Directory.
How severe is CVE-2008-6851?
CVE-2008-6851 has a CVSS v2 score of 5.1 (Medium) and an EPSS score of 0.88% (60th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.