CVE-2026-1551
BaseFortify
Publication date: 2026-01-29
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 | school_management_system | 1.0 |
Helpful Resources
Exploitability
| 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 Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not contain information regarding the impact of this SQL injection vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or mitigations have been reported for this vulnerability. The suggested immediate step is to replace the affected product with an alternative solution that does not have this vulnerability. [1]
Can you explain this vulnerability to me?
CVE-2026-1551 is a SQL injection vulnerability in itsourcecode School Management System version 1.0, specifically in the file /ramonsys/course/controller.php. 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 manipulate the SQL commands by injecting malicious code through the 'id' parameter. The attack can be performed remotely without authentication, making it easy for attackers to exploit. [1, 2, 4]
How can this vulnerability impact me? :
This vulnerability can compromise the confidentiality, integrity, and availability of the affected system. An attacker can perform unauthorized database operations, potentially accessing, modifying, or deleting sensitive data. Since the exploit is publicly available and can be executed remotely without authentication, it poses a significant risk of data breaches, data loss, or disruption of service. [1, 2, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by searching for the vulnerable URL pattern in your system or network, specifically targeting the file /ramonsys/course/controller.php with the 'id' parameter. One suggested method is using Google dorking with the query `inurl:ramonsys/course/controller.php` to identify potentially vulnerable targets. Additionally, testing the 'id' parameter for SQL injection by injecting typical SQL payloads (e.g., ' OR '1'='1) and observing the response can help detect the vulnerability. No specific commands are provided in the resources. [1]