CVE-2026-2073
Unknown Unknown - Not Provided
SQL Injection in itsourcecode School Management System Remote Exploit

Publication date: 2026-02-07

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability was determined in itsourcecode School Management System 1.0. This affects an unknown function of the file /ramonsys/user/index.php. Executing a manipulation of the argument ID can lead to sql injection. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-07
Last Modified
2026-04-29
Generated
2026-06-16
AI Q&A
2026-02-07
EPSS Evaluated
2026-06-15
NVD
CVE-2026-2073
EUVD
EUVD-2026-5759
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
itsourcecode school_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-2073 is a SQL injection vulnerability found in the itsourcecode School Management System version 1.0, specifically in the file /ramonsys/user/index.php.'}, {'type': 'paragraph', 'content': "The vulnerability occurs because the application does not properly sanitize or validate the 'id' parameter before using it in SQL queries. This allows an attacker to inject malicious SQL code remotely without needing to authenticate."}, {'type': 'paragraph', 'content': 'Exploiting this flaw enables unauthorized manipulation of the database, such as accessing sensitive data, tampering with data, or disrupting system operations.'}] [1, 2, 3]

Impact Analysis

This vulnerability can have serious impacts including unauthorized access to sensitive information, data tampering, and potential full system compromise.

  • Attackers can manipulate SQL queries to extract confidential data.
  • Data integrity can be compromised by unauthorized modifications.
  • Availability of the system can be affected through service interruptions.
  • The attack can be performed remotely without authentication, making exploitation straightforward.
Compliance Impact

I don't know

Detection Guidance

[{'type': 'paragraph', 'content': "This SQL injection vulnerability can be detected by testing the 'id' parameter in the URL of the affected file /ramonsys/user/index.php for injection flaws."}, {'type': 'paragraph', 'content': 'A proof-of-concept payload to test for time-based blind SQL injection is: view=edit&id=3 AND (SELECT 4321 FROM (SELECT(SLEEP(5)))wMXI), which causes a delay if the injection is successful.'}, {'type': 'paragraph', 'content': 'The sqlmap tool can be used to automate detection with a command like:'}, {'type': 'list_item', 'content': 'python sqlmap.py --random-agent --batch -u "http://<target-ip>:<port>/ramonsys/user/index.php?view=edit&id=3" --dbms=mysql -p id --current-db'}, {'type': 'paragraph', 'content': 'Additionally, vulnerable targets can be identified using Google dorking with the query: inurl:ramonsys/user/index.php'}] [2, 3]

Mitigation Strategies

Immediate mitigation steps include:

  • Use prepared statements and parameter binding to separate SQL code from user input, preventing injection.
  • Implement strict input validation and filtering to ensure inputs conform to expected formats, such as numeric patterns for IDs.
  • 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 or patches are documented, it is suggested to replace the affected product with an alternative if possible.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-2073. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart