Jtbc
10 vulnerabilities.
All published vulnerabilities with a CVE number in Jtbc products, newest first, with severity and references.
| CVE | Summary | Published | CVSS |
|---|---|---|---|
| CVE-2019-9662 | Jtbc Php: An issue was discovered in JTBC(PHP) 3.0.1.8. Its cache management module is flawed. An arbitrary file ending in "inc.php" can be deleted via a … | 2019-03-11 | 7.5 |
| CVE-2019-8433 | Jtbc Php: JTBC(PHP) 3.0.1.8 allows Arbitrary File Upload via the console/#/console/file/manage.php?type=list URI, as demonstrated by a .php file. | 2019-02-17 | 7.5 |
| CVE-2018-19547 | Jtbc Php: JTBC(PHP) 3.0.1.7 has XSS via the console/xml/manage.php?type=action&action=edit content parameter. | 2018-11-26 | 6.1 |
| CVE-2018-19546 | Jtbc Php: JTBC(PHP) 3.0.1.7 has CSRF via the console/xml/manage.php?type=action&action=edit URI, as demonstrated by an XSS payload in the content parameter. | 2018-11-26 | 8.8 |
| CVE-2018-19327 | Jtbc Php: An issue was discovered in JTBC(PHP) 3.0.1.7. aboutus/manage.php?type=action&action=add allows CSRF. | 2018-11-17 | 8.8 |
| CVE-2018-18436 | Jtbc Php: JTBC(PHP) 3.0 allows CSRF for creating an account via the console/account/manage.php?type=action&action=add URI. | 2018-10-17 | 8.8 |
| CVE-2018-17838 | Jtbc Php: An issue was discovered in JTBC(PHP) 3.0.1.6. Arbitrary file read operations are possible via a … | 2018-10-01 | 7.5 |
| CVE-2018-17837 | Jtbc Php: An issue was discovered in JTBC(PHP) 3.0.1.6. Arbitrary file deletion is possible via a … | 2018-10-01 | 7.5 |
| CVE-2018-17836 | Jtbc Php: An issue was discovered in JTBC(PHP) 3.0.1.6. It allows remote attackers to execute arbitrary PHP code by using a … | 2018-10-01 | 8.8 |
| CVE-2018-17429 | Jtbc: /console/account/manage.php?type=action&action=add in JTBC v3.0(C) has CSRF for adding an administrator account. | 2019-03-07 | 8.8 |
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Too many to
patch at once?
Providers for vulnerability management find the affected systems in your environment, set the order and keep the patching going.