CVE-2026-0582
Unknown Unknown - Not Provided
SQL Injection in itsourcecode SMS 1.0 /admin/edit_activity_query.php

Publication date: 2026-01-05

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability was identified in itsourcecode Society Management System 1.0. This affects an unknown part of the file /admin/edit_activity_query.php. The manipulation of the argument Title leads to sql injection. The attack may be initiated remotely. The exploit is publicly available and might be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-05
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2026-01-05
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
itsourcecode society_management_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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?

CVE-2026-0582 is a critical SQL injection vulnerability in the itsourcecode Society Management System version 1.0, specifically in the /admin/edit_activity_query.php file. It occurs due to improper handling and inadequate validation of the 'title' parameter, which allows attackers to inject malicious SQL queries. This enables unauthorized database access, data leakage, data tampering, and potentially full system control. The vulnerability can be exploited remotely without authentication using crafted payloads. [1, 2, 3]


How can this vulnerability impact me? :

Exploitation of this vulnerability can lead to unauthorized access to the database, allowing attackers to view, modify, or delete sensitive information. It can cause data leakage, data tampering, service disruption, and potentially full system compromise. This threatens system security, data integrity, and business continuity. [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/edit_activity_query.php endpoint for SQL injection. Attackers can use boolean-based blind and time-based blind SQL injection payloads, such as injecting boolean-based RLIKE conditions or time delays like SLEEP(5), to infer database behavior. Tools like sqlmap can be used to automate detection and confirm the vulnerability by enumerating the database. Additionally, Google dorking with queries like 'inurl:admin/edit_activity_query.php' can help identify vulnerable targets. [2, 3]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include replacing the affected component with an alternative product if possible. If not, implement prepared statements with parameter binding to separate SQL code from user input, apply strict input validation and filtering on the 'title' parameter, and minimize database user permissions by avoiding high-privilege accounts for routine operations. Conduct regular security audits to detect and fix vulnerabilities promptly. Since no known countermeasures are documented, these best practices are critical to reduce risk. [2, 3, 1]


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 lead to breaches of data confidentiality and integrity. Such breaches may result in non-compliance with data protection regulations like GDPR and HIPAA that require safeguarding personal and sensitive information. Therefore, exploitation of this vulnerability could negatively impact compliance with these standards by exposing protected data and failing to maintain required security controls. [1, 2, 3]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart