Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2013-3525: SQL Injection in Request Tracker 4.0.10 and earlier (ShowPending parameter)

Published May 10, 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
EPSS2.8%87th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Best Practical Solutions
IdentifiersCVE-2013-3525CWE-89 · Improper Neutralization of Special…

A reported SQL injection vulnerability exists in the Approvals/ component of Request Tracker (RT) versions 4.0.10 and earlier, where the ShowPending parameter is allegedly not properly sanitized, allowing remote attackers to execute arbitrary SQL commands. However, the vendor has disputed the validity of this vulnerability, stating that they were unable to replicate the issue and that the original reporter retracted their claim.

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.

If the vulnerability were valid, successful exploitation would allow remote attackers to execute arbitrary SQL commands against the RT database, potentially leading to data exfiltration, modification, or further compromise of the application. However, the vendor's statement casts doubt on the existence and exploitability of this issue.

Mitigation

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

As a general precaution, ensure that all user-supplied input is properly sanitized and parameterized in SQL queries. Monitor vendor advisories for any updates or patches. However, the vendor has stated that this specific issue could not be reproduced.

Remediation

Patch, then assume compromise.

No remediation is necessary according to the vendor, as they were unable to reproduce the issue and the original report was retracted. If concerned, users should ensure they are running the latest supported version of Request Tracker and follow secure coding practices for input validation.

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
Best Practical SolutionsRequest Trackerapplication
FAQ

Frequently asked questions

Is CVE-2013-3525 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2013-3525 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2013-3525?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2013-3525.
Is there a patch for CVE-2013-3525?
No remediation is necessary according to the vendor, as they were unable to reproduce the issue and the original report was retracted. If concerned, users should ensure they are running the latest supported version of Request Tracker and follow secure coding practices for input validation.
What products are affected by CVE-2013-3525?
Best Practical Solutions Request Tracker.
How severe is CVE-2013-3525?
CVE-2013-3525 has a CVSS v2 score of 7.5 (High) and an EPSS score of 2.8% (87th 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.