CVE-2020-15255 json
CSV injection in Anuko Time Tracker
published 6y ago modified 4mo ago also EUVD-2020-7266
- cvss
- 8.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.5%
- EPSS 3.5% chance of exploitation in 30 days, percentile 89%
- public exploits
- 1
- Exploit-DB
Summary
In Anuko Time Tracker before verion 1.19.23.5325, due to not properly filtered user input a CSV export of a report could contain cells that are treated as formulas by spreadsheet software (for example, when a cell value starts with an equal sign). This is fixed in version 1.19.23.5325.
Patch / fix
Is CVE-2020-15255 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-49027)
Exploit prediction
3.50% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-49027 Anuko Time Tracker 1.19.23.5325 - CSV/Formula Injection webapps, 2020-11-10
- packetstormsecurity.com http://packetstormsecurity.com/files/159996/Anuko-Time-Tracker-1.19.23.5325-CSV-Injection.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N |
| NVD | 3.1 | 7.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.0 | AV:N/AC:M/Au:S/C:P/I:P/A:P |
Affected products
- anuko timetracker
Classification
References
-
github.com
/anuko/timetracker/commit/d9472904361495f318c9d0294ffd28acaaeae42f
patch, third-party-advisory
-
packetstormsecurity.com
/files/159996/Anuko-Time-Tracker-1.19.23.5325-CSV-Injection.html
exploit, third-party-advisory, vdb-entry
-
exploit-db.com
/exploits/49027
exploit, third-party-advisory, vdb-entry
-
github.com
/anuko/timetracker/security/advisories/GHSA-prjf-9mgh-8fpv
third-party-advisory
Sources
- CVE List CVE-2020-15255
- NVD CVE-2020-15255
Fencer Intel 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.