CVE-2018-17837: An issue was discovered in JTBC(PHP) 3.0.1.6

This week

HIGH 7.5REMOTEDOWNGRADE

CVE-2018-17837 is a high-severity flaw (CVSS 7.5) affecting jtbc php. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue was discovered in JTBC(PHP) 3.0.1.6. Arbitrary file deletion is possible via a /console/file/manage.php?type=action&action=delete&path=c%3A%2F substring.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.3% (top 30%)
CISA exploited list	No
Weakness	CWE-22
Published	2018-10-01
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: jtbc

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-10-01 08:29 UTCPublished CVE record published
2026-06-17 01:46 UTCUpdated Record last modified

jtbc jtbc php DOWNGRADE

Affected: 3.0.1.6

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.0.1.6

1. Check installed version

apt-cache policy jtbc-php || rpm -q jtbc-php || jtbc-php --version

2. No fixed release: DOWNGRADE to a release before 3.0.1.6 (Debian / Ubuntu)

apt-cache madison jtbc-php sudo apt install jtbc-php=<VERSION_BEFORE_3.0.1.6> sudo apt-mark hold jtbc-php

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list jtbc-php sudo dnf downgrade jtbc-php-<VERSION_BEFORE_3.0.1.6> sudo dnf versionlock add jtbc-php

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-17837?

jtbc php: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2018-17837 being exploited?

CVE-2018-17837 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-17837 affect?

CVE-2018-17837 affects jtbc php. Severity is high (CVSS 7.5). An issue was discovered in JTBC(PHP) 3.0.1.6. Arbitrary file deletion is possible via a /console/file/manage.php?type=action&action=delete&path=c%3A%2F substring.

How urgent is CVE-2018-17837?

Priority 54/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

PHP vulnerabilities

Related CVEs

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

References

← Back to latest CVEs