Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

linkedin clone vulnerabilities and fixes

Recent CVEs affecting linkedin clone, with upgrade or downgrade steps. 1 tracked.

Also searched as: linkedinclone.

linkedin clone has 1 tracked vulnerability, 1 critical. A fixed release or vendor patch exists for 0. Most recent: 2017-12-13. Highest priority: CVE-2017-17580 (score 66/100).

FAQ

How do I fix linkedin clone vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is linkedin clone being exploited right now?

None of the tracked linkedin clone CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which linkedin clone CVE should I patch first?

CVE-2017-17580 currently ranks highest (66/100): FS Linkedin Clone 1.0 has SQL Injection via the group.php grid parameter, profile.php fid parameter, or compan.

← Back to latest CVEs