CVE-2026-3410
SQL Injection in itsourcecode Society Management System Admin Module
Publication date: 2026-03-02
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-3410 is a critical SQL injection vulnerability found in the itsourcecode Society Management System version 1.0. The flaw exists in the /admin/check_studid.php file due to improper handling and insufficient validation of the 'student_id' parameter."}, {'type': 'paragraph', 'content': 'This vulnerability allows attackers to inject malicious SQL queries remotely without authentication, enabling unauthorized access to the database.'}, {'type': 'paragraph', 'content': 'Exploitation can lead to unauthorized data modification, deletion, and exposure of sensitive information.'}] [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, data modification, and deletion.
Attackers can exploit the flaw remotely without any authentication, potentially gaining full control over the database and causing service disruptions.
- Exposure of sensitive information
- Unauthorized data modification and deletion
- Potential full system compromise
- Threats to system security and business continuity
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': "This vulnerability can be detected by testing the 'student_id' parameter in the /admin/check_studid.php file for SQL injection weaknesses. Techniques include using SQL injection payloads such as Boolean-based blind, error-based, and time-based blind SQL injection."}, {'type': 'list_item', 'content': "Boolean-based blind SQL injection payload example: student_id=11111111' OR NOT 5958=5958 #"}, {'type': 'list_item', 'content': "Error-based SQL injection payload example: student_id=11111111' OR (SELECT 1655 FROM(SELECT COUNT(*),CONCAT(0x717a717671,(SELECT (ELT(1655=1655,1))),0x7178787a71,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)--"}, {'type': 'list_item', 'content': "Time-based blind SQL injection payload example: student_id=11111111' AND (SELECT 5963 FROM (SELECT(SLEEP(5)))HUST)--"}, {'type': 'paragraph', 'content': 'Automated tools like sqlmap can be used to confirm the presence of the vulnerability by targeting the student_id parameter.'}, {'type': 'paragraph', 'content': 'Additionally, Google Dorking can help identify vulnerable targets using queries such as: inurl:admin/check_studid.php'}] [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input.
Enforce strict input validation and filtering to ensure that inputs conform to expected formats and do not contain malicious content.
Minimize database user permissions by avoiding the use of high-privilege accounts such as root or admin for routine database operations.
Conduct regular security audits of code and systems to detect and address vulnerabilities promptly.
If possible, replace the affected component or product with a secure alternative, as no known mitigations or countermeasures have been documented.