CVE-2026-1118
SQL Injection in itsourcecode SMS /admin/add_activity.php Allows Remote Exploit
Publication date: 2026-01-18
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| itsourcecode | society_management_system | 1.0 |
| angeljudesuarez | society_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
| 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. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized access, modification, and exposure of sensitive data through SQL injection, which can compromise confidentiality, integrity, and availability of the system. Such data breaches and unauthorized data manipulation can lead to non-compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive information. Therefore, this vulnerability poses a risk to compliance with these regulations by potentially exposing sensitive data and failing to maintain data security and privacy. [1, 2, 3]
Can you explain this vulnerability to me?
CVE-2026-1118 is a critical SQL injection vulnerability in the itsourcecode Society Management System version 1.0, specifically in the /admin/add_activity.php file. The vulnerability occurs because the 'title' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This flaw enables remote attackers to execute arbitrary SQL commands without authentication, potentially compromising the database and system security. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can allow attackers to gain unauthorized access to the database, leading to data leakage, modification, or deletion. It can also result in full system compromise or service disruption. Attackers can exploit the flaw remotely without authentication, using techniques such as boolean-based blind and time-based blind SQL injection. The impact includes loss of confidentiality, integrity, and availability of the system and its data. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'title' parameter in the /admin/add_activity.php file for SQL injection. You can use tools like sqlmap to automate detection and enumeration. Example payloads for manual testing include boolean-based blind injection using MySQL RLIKE operator: title=Hello' RLIKE (SELECT (CASE WHEN (5341=5341) THEN 0x48656c6c6f ELSE 0x28 END))-- and time-based blind injection causing delay with SLEEP function: title=Hello' RLIKE SLEEP(5)--. Additionally, attackers can locate vulnerable targets using Google dorking with the query inurl:admin/add_activity.php. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Implement strict input validation and filtering on the 'title' parameter to ensure inputs conform to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. 4) Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly. If possible, replace the affected component or product with a secure alternative. [1, 2, 3]