KLiK SocialMediaWebsite up to 1.0.1 Private Message get_message_ajax.php c_id sql injection
Summary
A vulnerability classified as critical has been found in KLiK SocialMediaWebsite up to 1.0.1. This issue affects some unknown processing of the file /includes/get_message_ajax.php of the component Private Message Handler. The manipulation of the argument c_id leads to sql injection. This vulnerability is documented as CVE-2026-7002. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability, which was classified as critical, has been found in KLiK SocialMediaWebsite up to 1.0.1. This issue affects some unknown processing of the file /includes/get_message_ajax.php of the component Private Message Handler. The manipulation of the argument c_id with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability.
The identification of this vulnerability is CVE-2026-7002. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/26/2026). MITRE ATT&CK project uses the attack technique T1505 for this issue.
By approaching the search of inurl:includes/get_message_ajax.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 EUVD (EUVD-2026-25677). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.3
VulDB Temp Score: 7.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Google Hack: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
04/24/2026 Advisory disclosed04/24/2026 VulDB entry created
04/26/2026 VulDB entry last update
Sources
Status: Not definedCVE: CVE-2026-7002 (🔒)
GCVE (CVE): GCVE-0-2026-7002
GCVE (VulDB): GCVE-100-359561
EUVD: 🔒
Entry
Created: 04/24/2026 22:27Updated: 04/26/2026 01:01
Changes: 04/24/2026 22:27 (52), 04/26/2026 01:01 (1)
Complete: 🔍
Submitter: g111
Cache ID: 216::103
Submit
Accepted
- Submit #797302: SourceCodester SourceCodester KLiK Social Media Website v1.0.1 SQL Injection (by g111)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.