CVE-2018-6610: Information Leakage exists in the jLike 1.0 component for Joomla! via a task=getUserByCommentId request.

This week

HIGH 7.5REMOTEDOWNGRADE

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

Information Leakage exists in the jLike 1.0 component for Joomla! via a task=getUserByCommentId request.

Why this priority

High severity
EPSS top 5%: very likely to be exploited
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	7.9% (top 5%)
CISA exploited list	No
Weakness	CWE-200
Published	2018-02-05
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: jlike project

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

Am I affected?

Timeline

2018-02-05 22:29 UTCPublished CVE record published
2026-06-17 02:02 UTCUpdated Record last modified

jlike project jlike DOWNGRADE

Affected: 1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0

1. Check installed version

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

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

apt-cache madison jlike sudo apt install jlike=<VERSION_BEFORE_1.0> sudo apt-mark hold jlike

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

dnf --showduplicates list jlike sudo dnf downgrade jlike-<VERSION_BEFORE_1.0> sudo dnf versionlock add jlike

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.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: Joomla! Component jLike 1.0 - Information Leak

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

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

Is CVE-2018-6610 being exploited?

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

CVE-2018-6610 affects jlike. Severity is high (CVSS 7.5). Information Leakage exists in the jLike 1.0 component for Joomla! via a task=getUserByCommentId request.

How urgent is CVE-2018-6610?

Priority 60/100. High severity; EPSS top 5%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Joomla vulnerabilities

References

← Back to latest CVEs