Facebook Clone Script 1.0 friend-profile.php ID sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Facebook Clone Script 1.0. It has been declared as critical. This issue affects some unknown processing of the file friend-profile.php. Executing a manipulation of the argument ID as part of Parameter can lead to sql injection. This vulnerability is registered as CVE-2017-17615. It is possible to launch the attack remotely. Furthermore, an exploit is available.
Details
A vulnerability classified as critical was found in Facebook Clone Script 1.0 (Social Network Software). This vulnerability affects some unknown processing of the file friend-profile.php. The manipulation of the argument id as part of a Parameter leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
Facebook Clone Script 1.0 has SQL Injection via the friend-profile.php id parameter.
The bug was discovered 05/29/2018. The weakness was published 12/13/2017 (Website). The advisory is shared for download at packetstormsecurity.com. This vulnerability was named CVE-2017-17615 since 12/13/2017. The exploitation appears to be easy. The attack can be initiated remotely. Required for exploitation is a single authentication. Technical details and also a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1505.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:friend-profile.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Exploit-DB (43280). Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.2
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/13/2017 🔍12/13/2017 🔍
12/13/2017 🔍
12/13/2017 🔍
05/29/2018 🔍
08/29/2025 🔍
Sources
Advisory: 145320Status: Not defined
CVE: CVE-2017-17615 (🔍)
GCVE (CVE): GCVE-0-2017-17615
GCVE (VulDB): GCVE-100-110620
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 12/13/2017 14:16Updated: 08/29/2025 11:14
Changes: 12/13/2017 14:16 (58), 12/14/2019 16:08 (4), 01/17/2023 19:24 (4), 08/29/2025 11:14 (18)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.