CVE-2026-2116

7.3

itsourcecode · Society Management System

A SQL injection vulnerability in the Society Management System allows remote, unauthenticated attackers to manipulate database queries via the expenses_id parameter in edit_expenses.php.

Executive summary

A critical SQL injection vulnerability in itsourcecode Society Management System 1.0 exposes the application to remote, unauthenticated database manipulation.

Vulnerability

The application is susceptible to SQL injection via the expenses_id parameter within the /admin/edit_expenses.php file. This flaw allows unauthenticated remote attackers to execute arbitrary SQL commands, as the application fails to properly sanitize user input.

Business impact

Successful exploitation of this vulnerability can lead to unauthorized access to sensitive database information, potential data modification, or service disruption. Given the CVSS score of 7.3, this represents a high-severity risk that could compromise the integrity and confidentiality of the entire system management platform.

Remediation

Immediate Action: As no official patch is currently available, administrators should restrict access to the /admin/ directory to trusted IP addresses or disable the affected module entirely if it is not business critical.

Proactive Monitoring: Review web server and database logs for anomalous query patterns, specifically looking for SQL syntax characters such as single quotes, semicolons, or comment indicators in requests directed at edit_expenses.php.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block common SQL injection patterns to mitigate the risk until a vendor-supplied update is released.

Exploitation status

Public Exploit Available: Yes, a published proof-of-concept exists, as documented in the linked GitHub issue tracker.

Analyst recommendation

Due to the availability of a public proof-of-concept and the ease of exploitation, this vulnerability poses a significant risk to affected installations. Organizations should prioritize isolating the vulnerable component from external access immediately and monitor for any signs of unauthorized database interaction until a formal security update is provided by the vendor.

More itsourcecode CVEs

Sources

Originally found and disclosed by oblong (VulDB User), per the CVE Program record.