CVE-2018-17429: /console/account/manage.php?type=action&action=add in JTBC v3.0(C) has CSRF for adding an administrator accoun

This month

HIGH 8.8DOWNGRADE

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

/console/account/manage.php?type=action&action=add in JTBC v3.0(C) has CSRF for adding an administrator account.

Why this priority

High severity
Public exploit reference

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

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.6% (top 51%)
CISA exploited list	No
Weakness	CWE-352
Published	2019-03-07
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

2019-03-07 23:29 UTCPublished CVE record published
2026-06-17 01:45 UTCUpdated Record last modified

jtbc jtbc DOWNGRADE

Affected: 3.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.0

1. Check installed version

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

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

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

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

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

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-17429?

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

Is CVE-2018-17429 being exploited?

CVE-2018-17429 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-17429 affect?

CVE-2018-17429 affects jtbc. Severity is high (CVSS 8.8). /console/account/manage.php?type=action&action=add in JTBC v3.0(C) has CSRF for adding an administrator account.

How urgent is CVE-2018-17429?

Priority 48/100. High severity; Public exploit reference

Software pages

PHP vulnerabilities

References

← Back to latest CVEs