CVE-2013-3525: SQL Injection

Published May 10, 2013
·
Updated

DISPUTED SQL injection vulnerability in Approvals/ in Request Tracker (RT) 4.0.10 and earlier allows remote attackers to execute arbitrary SQL commands via the ShowPending parameter. NOTE: the vendor disputes this issue, stating "We were unable to replicate it, and the individual that reported it retracted their report," and "we had verified that the claimed exploit did not function according to the author's claims."

Affected Software

24 affected components
bestpractical Request Tracker<=4.0.9
bestpractical Request Tracker=3.6.8
bestpractical Request Tracker=3.6.10
bestpractical Request Tracker=3.6.11
bestpractical Request Tracker=3.8.3
bestpractical Request Tracker=3.8.4
bestpractical Request Tracker=3.8.7
bestpractical Request Tracker=3.8.9
bestpractical Request Tracker=3.8.10
bestpractical Request Tracker=3.8.11
bestpractical Request Tracker=3.8.12
bestpractical Request Tracker=3.8.13
bestpractical Request Tracker=3.8.14
bestpractical Request Tracker=3.8.15
bestpractical Request Tracker=3.8.16
bestpractical Request Tracker=4.0.0
bestpractical Request Tracker=4.0.1
bestpractical Request Tracker=4.0.2
bestpractical Request Tracker=4.0.3
bestpractical Request Tracker=4.0.4
bestpractical Request Tracker=4.0.5
bestpractical Request Tracker=4.0.6
bestpractical Request Tracker=4.0.7
bestpractical Request Tracker=4.0.8

Event History

May 10, 2013
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description
Disputed
09:55 PM

Frequently Asked Questions

1

What is the severity of CVE-2013-3525?

The severity of CVE-2013-3525 is disputed, as the vendor states they could not replicate the SQL injection vulnerability.

2

How do I fix CVE-2013-3525?

Since the vendor disputes the existence of the vulnerability, there are no official fixes, but users are encouraged to maintain the latest version of Request Tracker.

3

Who is affected by CVE-2013-3525?

CVE-2013-3525 affects Request Tracker versions 4.0.10 and earlier, as well as several versions of Request Tracker 3.x.

4

What types of attacks are possible with CVE-2013-3525?

CVE-2013-3525 allows for potential execution of arbitrary SQL commands through the ShowPending parameter in affected Request Tracker versions.

5

Is CVE-2013-3525 widely exploited?

There is no public indication that CVE-2013-3525 has been widely exploited, but users should monitor for any unusual activity.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203