Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAccess vulnerable AJAX endpoint
-
DeliveryInject SQL payload in c_id parameter
-
ExploitExecute unauthorized database queries
-
ExecutionExtract private messages and user data
-
ImpactEscalate to credential theft or further database manipulation
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the /includes/get_message_ajax.php endpoint to be network-accessible to the attacker, which is typical for AJAX endpoints in web applications. The CVSS vector PR:N confirms no authentication is required - the vulnerable endpoint processes requests from unauthenticated users. Successful exploitation depends on the specific SQL query structure and database permissions: attackers can inject arbitrary SQL, but actual impact (data extraction scope, write capabilities, command execution via database features) varies based on backend database type (MySQL, PostgreSQL, etc.), application database user privileges, and query construction. The 'Private Message Handler' component designation suggests the endpoint queries conversation or messaging tables, which may contain sensitive user communications. No special client-side conditions, user interaction, or non-default configurations are required based on UI:N in the CVSS vector. |
| Impact | The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates this is remotely exploitable without authentication, presenting a significant attack surface for internet-facing deployments. However, real-world risk depends heavily on deployment context. The CVSS 7.3 score reflects partial CIA impact (C:L/I:L/A:L), suggesting exploitation may be constrained by database permissions, application logic, or query structure rather than complete database takeover. No EPSS score provided, but absence from CISA KEV and lack of public POC in references suggest exploitation has not become widespread or automated. The VulDB submission indicates researcher disclosure rather than in-the-wild observation. Primary risk is to organizations running internet-accessible instances of KLiK SocialMediaWebsite 1.0.1 or earlier, particularly those storing sensitive user data in private messages. Applications behind authentication layers, WAFs with SQL injection signatures, or those with read-only database permissions face reduced practical risk despite the high CVSS rating. Missing vendor advisory and patch information creates uncertainty about remediation timeline. |
| Exploit ScenarioDerived | An unauthenticated attacker identifies KLiK SocialMediaWebsite from fingerprinting and crafts a malicious HTTP request to /includes/get_message_ajax.php with a c_id parameter containing SQL injection payload such as '1 UNION SELECT username,password,email FROM users--'. The vulnerable PHP code concatenates this input directly into a SQL query without sanitization, executing the attacker's injected commands. The attacker extracts private message contents, user credentials, or other database contents depending on application database schema and permissions, potentially pivoting to account takeover or broader system compromise. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 25, 2026
SQL injection in KLiK SocialMediaWebsite 1.0.1 and earlier allows remote unauthenticated attackers to execute arbitrary SQL commands via the c_id parameter in /includes/get_message_ajax.php. The vulnerability targets the private message handling component and permits unauthorized database access, modification, and potential data exfiltration. CVSS 7.3 reflects network-accessible, low-complexity exploitation requiring no authentication or user interaction, with partial impact to confidentiality, integrity, and availability. No public exploit code or CISA KEV listing identified at time of analysis, suggesting limited observed exploitation despite the accessible attack surface.
RemediationAI
No vendor-released patch or fixed version has been identified in available intelligence sources. In the absence of official patches, implement these compensating controls: Deploy a web application firewall (WAF) with SQL injection detection rules to filter malicious c_id parameter values before they reach the application - note this adds latency and requires ongoing signature updates. Restrict network access to /includes/get_message_ajax.php to authenticated sessions only through web server configuration (Apache mod_rewrite or nginx location blocks) - this reduces attack surface but may break legitimate AJAX functionality if the application expects unauthenticated access. Implement database user permission restrictions limiting the web application's database account to minimum required privileges, preventing SELECT queries from accessing sensitive tables and blocking DELETE/UPDATE/DROP operations entirely - this contains damage but does not prevent data exfiltration from accessible tables. Monitor application logs for suspicious c_id parameter patterns including SQL keywords, comment sequences, or union-based injection attempts. Check vendor channels and https://vuldb.com/vuln/359561 for patch announcements. If private messaging functionality is non-critical, disable the vulnerable endpoint entirely until patches are available.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This is a classic SQL injection vulnerability (CWE-89) in a PHP-based social media application. The /includes/get_message_ajax.php endpoint, part of the private messaging system, fails to properly sanitize or parameterize the c_id parameter before incorporating it into SQL queries. Based on the CPE (cpe:2.3:a:klik:socialmediawebsite), this affects KLiK's SocialMediaWebsite application version 1.0.1 and potentially earlier versions. The vulnerability class indicates direct concatenation of user-supplied input into database queries without input validation, prepared statements, or adequate escaping. As an AJAX endpoint handling private messages, this component likely queries user conversation data, making it a high-value target for attackers seeking to access sensitive communications, manipulate message histories, or pivot to broader database compromise.
Know when Klik gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
Primary rating from Vendor (VulDB) · only source for this CVE.
CVSS VectorVendor: VulDB
Lifecycle Timeline
3DescriptionCVE.org
A vulnerability was determined in KLiK SocialMediaWebsite up to 1.0.1. This vulnerability affects unknown code of the file /includes/get_message_ajax.php of the component Private Message Handler. Executing a manipulation of the argument c_id can lead to sql injection. It is possible to launch the attack remotely.
Executive ViewAI
KLiK SocialMediaWebsite versions 1.0.1 and earlier contain an unauthenticated SQL injection vulnerability in the private message handling component that allows remote attackers to access, modify, or exfiltrate database contents without credentials. Organizations running this software face immediate risk of unauthorized data access and potential compromise of user private messages and associated database records until mitigation is deployed.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Deploy WAF rules to block SQL injection syntax in c_id parameter and /includes/get_message_ajax.php requests; (2) Restrict network access to the affected application via firewall rules limiting exposure to trusted networks only; (3) Implement database-level access controls and enable query logging to detect exploitation attempts; (4) Apply input validation and prepared statements at application layer to neutralize SQL injection vectors pending vendor patch availability.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
KLiK SocialMediaWebsite Version 1.0.1 has XSS vulnerabilities that allow attackers to store XSS via location input reply
KLiK SocialMediaWebsite Version 1.0.1 has XSS vulnerabilities that allow attackers to store XSS via location Forum Subje
EUVD-2026-25677
NVD
CVE.org
EPSS
Vulnrichment
VulDB
GitHub PoC
Exploit-DB