CVE-2022-4889 json
visegripped Stracker api.php getHistory sql injection
published 2023-01-15 3 y ago modified 2026-06-17 4 mo ago also EUVD-2022-52147
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
A vulnerability classified as critical was found in visegripped Stracker. Affected by this vulnerability is the function getHistory of the file doc_root/public_html/stracker/api.php. The manipulation of the argument symbol/startDate/endDate leads to sql injection. The identifier of the patch is 63e1b040373ee5b6c7d1e165ecf5ae1603d29e0a. It is recommended to apply a patch to fix this issue. The identifier VDB-218377 was assigned to this vulnerability.
Patch / fix
- stracker_project stracker 2022-04-09
- github.com/visegripped/stracker@63e1b04 commit
- github.com/visegripped/stracker#16 pull request
Exploit prediction
0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
| CNA | 3.0 | 5.5 | CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
| CNA | 2.0 | 5.2 | AV:A/AC:L/Au:S/C:P/I:P/A:P |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- visegripped Stracker
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
github.com
/visegripped/stracker/pull/16
issue-tracking, patch
-
github.com
/visegripped/stracker/commit/63e1b040373ee5b6c7d1e165ecf5ae1603d29e0a
patch
-
vuldb.com
/?id.218377
vdb-entry, technical-description, permissions-required
-
vuldb.com
/?ctiid.218377
signature, permissions-required
Sources
- CVE List CVE-2022-4889
- NVD CVE-2022-4889
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.