Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2013-5121: SQL Injection in PHPFox <3.6.0 (build6) via search[sort_by]

Published Aug 14, 2013 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v2
EPSS1.1%67th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Phpfox
IdentifiersCVE-2013-5121CWE-89 · Improper Neutralization of Special…

A SQL injection vulnerability exists in PHPFox versions prior to 3.6.0 (build6). The vulnerability is present in the handling of the 'search[sort_by]' parameter in the user/browse/view_/ endpoint, where user-supplied input is not properly sanitized before being incorporated into SQL queries. This allows remote attackers to inject arbitrary SQL commands into the application's database queries.

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 PHPFox application's database. This can lead to unauthorized data access, data modification, or deletion, and potentially full compromise of the application if further chained with other vulnerabilities.

Mitigation

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

If immediate upgrade is not possible, implement strict input validation and sanitization on the 'search[sort_by]' parameter, and consider using parameterized queries or prepared statements to prevent SQL injection. Additionally, restrict database user privileges to minimize the impact of a successful attack.

Remediation

Patch, then assume compromise.

Upgrade PHPFox to version 3.6.0 (build6) or later, where the input validation and sanitization for the affected parameter has been properly implemented to prevent SQL injection.

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
PhpfoxPhpfoxapplication
FAQ

Frequently asked questions

Is CVE-2013-5121 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2013-5121 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2013-5121?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2013-5121.
Is there a patch for CVE-2013-5121?
Upgrade PHPFox to version 3.6.0 (build6) or later, where the input validation and sanitization for the affected parameter has been properly implemented to prevent SQL injection.
What products are affected by CVE-2013-5121?
Phpfox.
How severe is CVE-2013-5121?
CVE-2013-5121 has a CVSS v2 score of 7.5 (High) and an EPSS score of 1.1% (67th 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.