CVE-2026-2117
SQL Injection in itsourcecode SMS 1.0 /admin/edit_activity.php
Publication date: 2026-02-08
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 |
|---|---|---|
| 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
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-2117 is a critical SQL injection vulnerability found in the itsourcecode Society Management System version 1.0, specifically in the file /admin/edit_activity.php.'}, {'type': 'paragraph', 'content': "The vulnerability arises because the 'activity_id' parameter is not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without authentication."}, {'type': 'paragraph', 'content': 'Exploitation of this flaw can lead to unauthorized access to the database, enabling attackers to view, modify, or delete sensitive data.'}] [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized database access, data leakage, data modification, and deletion.
Attackers can exploit this remotely without any authentication, potentially leading to full system compromise or service disruption.
- Exposure of sensitive information
- Unauthorized modification or deletion of data
- Potential full system compromise
- Service disruption
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': "The vulnerability can be detected by testing the 'activity_id' parameter in the /admin/edit_activity.php file for SQL injection flaws."}, {'type': 'paragraph', 'content': 'Testing can be performed using SQL injection payloads such as boolean-based blind and time-based blind injections.'}, {'type': 'list_item', 'content': "Boolean-based blind payload example: activity_id=2' RLIKE (SELECT (CASE WHEN (3804=3804) THEN 2 ELSE 0x28 END))--"}, {'type': 'list_item', 'content': "Time-based blind payload example: activity_id=2' AND 6596=BENCHMARK(5000000,MD5(0x4f724952))--"}, {'type': 'paragraph', 'content': 'Tools like sqlmap can be used to automate detection and exploitation attempts to confirm the presence of the vulnerability.'}, {'type': 'paragraph', 'content': 'Additionally, vulnerable targets can be identified using Google dorking with the query: inurl:admin/edit_activity.php'}] [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing or patching the affected component or product, as no known countermeasures are currently available.
Recommended remediation measures are:
- Use prepared statements with parameter binding to separate SQL code from user input, preventing injection.
- Implement strict input validation and filtering to ensure inputs conform to expected formats.
- Minimize database user permissions by avoiding use of high-privilege accounts (e.g., root or admin) for routine operations.
- Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly.