CVE-2013-3525
CVE-2013-3525 is a high-severity vulnerability in Bestpractical Request Tracker with a CVSS 2.0 base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-89.
Key facts
- Severity: High (CVSS 2.0 base score 7.5)
- EPSS exploit prediction: 3% (85th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-89
- Affected product: Bestpractical Request Tracker
- Published:
- Last modified:
Description
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.
Frequently asked questions
- What is CVE-2013-3525?
- 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.
- How severe is CVE-2013-3525?
- CVE-2013-3525 has a CVSS 2.0 base score of 7.5, rated high severity.
- Is CVE-2013-3525 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (85th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2013-3525?
- CVE-2013-3525 primarily affects Bestpractical Request Tracker. In total, 24 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2013-3525?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2013-3525 published?
- CVE-2013-3525 was published on 2013-05-10 and last updated on 2026-06-16.
References
- http://blog.bestpractical.com/2013/04/on-our-security-policies.html
- http://cxsecurity.com/issue/WLB-2013040083
- http://osvdb.org/92265
- http://packetstormsecurity.com/files/121245/RT-Request-Tracker-4.0.10-SQL-Injection.html
- http://www.securityfocus.com/bid/59022
- https://exchange.xforce.ibmcloud.com/vulnerabilities/83375
Affected products (24)
- cpe:2.3:a:bestpractical:request_tracker:*:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:3.6.8:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:3.6.10:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:3.6.11:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:3.8.3:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:3.8.4:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:3.8.7:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:3.8.9:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:3.8.10:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:3.8.11:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:3.8.12:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:3.8.13:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:3.8.14:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:3.8.15:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:3.8.16:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:4.0.0:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:4.0.1:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:4.0.2:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:4.0.3:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:4.0.4:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:4.0.5:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:4.0.6:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:4.0.7:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:4.0.8:*:*:*:*:*:*:*
More vulnerabilities in Bestpractical Request Tracker
- CVE-2017-5944 — High (CVSS 8.8): The dashboard subscription interface in Request Tracker (RT) 4.x before 4.0.25, 4.2.x before 4.2.14, and 4.4.x before…
- CVE-2017-5943 — High (CVSS 8.8): Request Tracker (RT) 4.x before 4.0.25, 4.2.x before 4.2.14, and 4.4.x before 4.4.2 allows remote attackers to obtain…
- CVE-2023-45024 — High (CVSS 7.5): Best Practical Request Tracker (RT) 5 before 5.0.5 allows Information Disclosure via a transaction search in the…
- CVE-2023-41260 — High (CVSS 7.5): Best Practical Request Tracker (RT) before 4.4.7 and 5.x before 5.0.5 allows Information Exposure in responses to…
- CVE-2023-41259 — High (CVSS 7.5): Best Practical Request Tracker (RT) before 4.4.7 and 5.x before 5.0.5 allows Information Disclosure via fake or spoofed…
- CVE-2021-38562 — High (CVSS 7.5): Best Practical Request Tracker (RT) 4.2 before 4.2.17, 4.4 before 4.4.5, and 5.0 before 5.0.2 allows sensitive…
All CVEs affecting Bestpractical Request Tracker →
Other CWE-89 (SQL Injection) vulnerabilities
- CVE-2026-54350 — Critical (CVSS 10.0): Budibase is an open-source low-code platform. Prior to 3.39.12, an unauthenticated visitor of any published Budibase…
- CVE-2026-8054 — Critical (CVSS 10.0): Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in the Publish Audit API endpoints…
- CVE-2026-42287 — Critical (CVSS 10.0): Emlog is an open source website building system. Prior to version 2.6.11, direct SQL injection in article creation and…
- CVE-2026-3325 — Critical (CVSS 10.0): SQL injection (SQLi) in MegaCMS v12.0.0, specifically in the “id_territorio” parameter of the…
- CVE-2025-10878 — Critical (CVSS 10.0): A SQL injection vulnerability exists in the login functionality of Fikir Odalari AdminPando 1.0.1 before 2026-01-26.…
- CVE-2025-57792 — Critical (CVSS 10.0): Explorance Blue versions prior to 8.14.9 contain a SQL injection vulnerability caused by insufficient validation of…