CVE-2017-17580: FS Linkedin Clone 1.0 has SQL Injection via the group.php grid parameter, profile.php fid parameter, or compan

This week

CRITICAL 9.8REMOTEDOWNGRADE

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

FS Linkedin Clone 1.0 has SQL Injection via the group.php grid parameter, profile.php fid parameter, or company_details.php 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	3.0% (top 13%)
CISA exploited list	No
Weakness	CWE-89
Published	2017-12-13
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: linkedin clone project

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

Am I affected?

Timeline

2017-12-13 09:29 UTCPublished CVE record published
2026-06-17 01:11 UTCUpdated Record last modified

linkedin clone project linkedin clone 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 linkedin-clone || rpm -q linkedin-clone || linkedin-clone --version

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

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

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

dnf --showduplicates list linkedin-clone sudo dnf downgrade linkedin-clone-<VERSION_BEFORE_1.0> sudo dnf versionlock add linkedin-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.

Exploit-DB: FS Linkedin Clone 1.0 - 'grid' / 'fid' / 'id' SQL Injection

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

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

Is CVE-2017-17580 being exploited?

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

CVE-2017-17580 affects linkedin clone. Severity is critical (CVSS 9.8). FS Linkedin Clone 1.0 has SQL Injection via the group.php grid parameter, profile.php fid parameter, or company_details.php id parameter.

How urgent is CVE-2017-17580?

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

Software pages

PHP vulnerabilities

References

← Back to latest CVEs