CVE-2018-17399: SQL Injection exists in the Jimtawl 2.2.7 component for Joomla! via the id parameter.

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2018-17399 is a critical-severity flaw (CVSS 9.8) affecting jimtawl. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

SQL Injection exists in the Jimtawl 2.2.7 component for Joomla! via the id parameter.

Why this priority

Critical 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	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.3% (top 17%)
CISA exploited list	No
Weakness	CWE-89
Published	2019-06-19
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: jimtawl project

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

Am I affected?

Timeline

2019-06-19 17:15 UTCPublished CVE record published
2026-06-17 01:45 UTCUpdated Record last modified

jimtawl project jimtawl DOWNGRADE

Affected: 2.2.7

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.2.7

1. Check installed version

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

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

apt-cache madison jimtawl sudo apt install jimtawl=<VERSION_BEFORE_2.2.7> sudo apt-mark hold jimtawl

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

dnf --showduplicates list jimtawl sudo dnf downgrade jimtawl-<VERSION_BEFORE_2.2.7> sudo dnf versionlock add jimtawl

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

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

Is CVE-2018-17399 being exploited?

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

CVE-2018-17399 affects jimtawl. Severity is critical (CVSS 9.8). SQL Injection exists in the Jimtawl 2.2.7 component for Joomla! via the id parameter.

How urgent is CVE-2018-17399?

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

Software pages

Joomla vulnerabilities

Related CVEs

CVE-2018-6580 CRITICAL 9.8 DOWNGRADE Arbitrary file upload exists in the Jimtawl 2.1.6 and 2.2.5 component for Joomla! via a view=upload&task=uploa

References

← Back to latest CVEs