CVE-2026-2117
Unknown Unknown - Not Provided
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
A vulnerability was found in itsourcecode Society Management System 1.0. The affected element is an unknown function of the file /admin/edit_activity.php. Performing a manipulation of the argument activity_id results in sql injection. The attack can be initiated remotely. The exploit has been made public and could be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-08
Last Modified
2026-04-29
Generated
2026-06-16
AI Q&A
2026-02-08
EPSS Evaluated
2026-06-14
NVD
CVE-2026-2117
EUVD
EUVD-2026-6751
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
angeljudesuarez society_management_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
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.
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.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

[{'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]

Impact Analysis

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
Compliance Impact

I don't know

Detection Guidance

[{'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]

Mitigation Strategies

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.
Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-2117. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart