CVE-2026-1119
SQL Injection in itsourcecode Society Management System /admin/delete_activity.php
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)?:
This vulnerability allows unauthorized access, modification, and leakage of sensitive data due to SQL injection, which can lead to violations of data protection regulations such as GDPR and HIPAA. Exploitation of this flaw compromises confidentiality, integrity, and availability of data, potentially resulting in non-compliance with these standards that require safeguarding personal and sensitive information. Therefore, organizations using the affected system may face compliance risks if the vulnerability is not remediated promptly. [1, 3, 4]
Can you explain this vulnerability to me?
CVE-2026-1119 is a critical SQL injection vulnerability in the itsourcecode Society Management System version 1.0, specifically in the /admin/delete_activity.php file. The vulnerability arises because the activity_id parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, potentially leading to unauthorized database access, data leakage, data manipulation, and disruption of services. [1, 3, 4]
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized access to the database, leakage of sensitive data, modification or deletion of data, and potential full system compromise or service disruption. Since no authentication is required to exploit it, attackers can remotely launch attacks that may affect system security and business continuity. [1, 3, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /admin/delete_activity.php endpoint for SQL injection via the activity_id parameter. You can use sqlmap, an automated SQL injection tool, to test for this vulnerability. Example command: sqlmap -u "http://targetsite/admin/delete_activity.php?activity_id=1" --batch --level=5 --risk=3. Additionally, proof-of-concept payloads include boolean-based blind SQL injection such as: activity_id=2' RLIKE (SELECT (CASE WHEN (3804=3804) THEN 2 ELSE 0x28 END))-- AiDD and time-based blind SQL injection like: activity_id=2' AND 6596=BENCHMARK(5000000,MD5(0x4f724952))-- spQb. These payloads can be used in manual testing or with tools to detect the vulnerability. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Implement strict input validation and filtering to ensure inputs conform to expected formats. 3) Minimize database user permissions, avoiding use of high-privilege accounts like root or admin for routine operations. 4) Conduct regular security audits to detect and address vulnerabilities promptly. If possible, replace the affected component with an alternative product or patch the vulnerable code to fix the input sanitization issue. [1, 4]