Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2017-17612: Hot Scripts Clone 3.1 has SQL Injection via the /categories subctid or mctid parameter.

67
This week
CRITICAL 9.8REMOTEDOWNGRADE

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

Hot Scripts Clone 3.1 has SQL Injection via the /categories subctid or mctid 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 score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance3.7% (top 10%)
CISA exploited listNo
WeaknessCWE-89
Published2017-12-13
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: hot scripts clone project

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

hot scripts clone project hot scripts clone DOWNGRADE
Affected: 3.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 3.1
1. Check installed version
apt-cache policy hot-scripts-clone || rpm -q hot-scripts-clone || hot-scripts-clone --version
2. No fixed release: DOWNGRADE to a release before 3.1 (Debian / Ubuntu)
apt-cache madison hot-scripts-clone sudo apt install hot-scripts-clone=<VERSION_BEFORE_3.1> sudo apt-mark hold hot-scripts-clone
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list hot-scripts-clone sudo dnf downgrade hot-scripts-clone-<VERSION_BEFORE_3.1> sudo dnf versionlock add hot-scripts-clone
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.

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-2017-17612?

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

Is CVE-2017-17612 being exploited?

CVE-2017-17612 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-2017-17612 affect?

CVE-2017-17612 affects hot scripts clone. Severity is critical (CVSS 9.8). Hot Scripts Clone 3.1 has SQL Injection via the /categories subctid or mctid parameter.

How urgent is CVE-2017-17612?

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

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.