PatchTheCVEjtbc php vulnerabilities and fixes
Recent CVEs affecting jtbc php, with upgrade or downgrade steps. 9 tracked.
Also searched as: jtbcphp.
jtbc php has 9 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2019-03-11. Highest priority: CVE-2019-9662 (score 55/100).
- CVE-2019-9662 HIGH 7.5 DOWNGRADE An issue was discovered in JTBC(PHP) 3.0.1.8
- CVE-2019-8433 HIGH 7.5 DOWNGRADE JTBC(PHP) 3.0.1.8 allows Arbitrary File Upload via the console/#/console/file/manage.php?type=list URI, as dem
- CVE-2018-19547 MEDIUM 6.1 DOWNGRADE JTBC(PHP) 3.0.1.7 has XSS via the console/xml/manage.php?type=action&action=edit content parameter.
- CVE-2018-19546 HIGH 8.8 DOWNGRADE JTBC(PHP) 3.0.1.7 has CSRF via the console/xml/manage.php?type=action&action=edit URI, as demonstrated by an X
- CVE-2018-19327 HIGH 8.8 DOWNGRADE An issue was discovered in JTBC(PHP) 3.0.1.7
- CVE-2018-18436 HIGH 8.8 DOWNGRADE JTBC(PHP) 3.0 allows CSRF for creating an account via the console/account/manage.php?type=action&action=add UR
- CVE-2018-17838 HIGH 7.5 DOWNGRADE An issue was discovered in JTBC(PHP) 3.0.1.6
- CVE-2018-17837 HIGH 7.5 DOWNGRADE An issue was discovered in JTBC(PHP) 3.0.1.6
- CVE-2018-17836 HIGH 8.8 DOWNGRADE An issue was discovered in JTBC(PHP) 3.0.1.6
FAQ
How do I fix jtbc php vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is jtbc php being exploited right now?
None of the tracked jtbc php CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which jtbc php CVE should I patch first?
CVE-2019-9662 currently ranks highest (55/100): An issue was discovered in JTBC(PHP) 3.0.1.8.