CVE-2026-2090
Unknown Unknown - Not Provided
SQL Injection in SourceCodester Online Class Record System Remote

Publication date: 2026-02-07

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability was determined in SourceCodester Online Class Record System 1.0. This issue affects some unknown processing of the file /admin/message/search.php. Executing a manipulation of the argument term can lead to sql injection. The attack can be executed remotely. 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-05-27
AI Q&A
2026-02-07
EPSS Evaluated
2026-05-25
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
janobe online_class_record_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 Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-2090 is a critical SQL injection vulnerability found in SourceCodester Online Class Record System version 1.0, specifically in the file `/admin/message/search.php`.

The vulnerability arises from improper handling of the `term` parameter, which is used in constructing SQL queries without adequate sanitization or neutralization of special characters.

This flaw allows remote attackers to execute arbitrary SQL commands without requiring authentication, impacting the confidentiality, integrity, and availability of the system.

Attackers can exploit this vulnerability remotely by injecting malicious SQL code through the `term` parameter, potentially using techniques such as Boolean-based blind SQL injection, time-based blind SQL injection, and UNION-based SQL injection.


How can this vulnerability impact me? :

Exploitation of this vulnerability can lead to unauthorized database access, allowing attackers to retrieve, modify, or delete sensitive data.

Attackers may gain full system control, cause service interruptions, and compromise the confidentiality, integrity, and availability of the affected system.

The attack can be executed remotely without authentication, making it easy for attackers to exploit and potentially cause significant damage.


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 /admin/message/search.php endpoint for SQL injection via the 'term' parameter. Attackers and testers can use SQL injection payloads such as boolean-based blind, time-based blind, or UNION-based injections to verify the flaw."}, {'type': 'paragraph', 'content': 'Example commands using sqlmap to detect the vulnerability include:'}, {'type': 'list_item', 'content': 'sqlmap -u "http://target/admin/message/search.php?term=test" --dbs'}, {'type': 'list_item', 'content': 'sqlmap -u "http://target/admin/message/search.php?term=test" --technique=BEUSTQ'}, {'type': 'paragraph', 'content': 'Additionally, Google dorking can help identify vulnerable targets by searching for: inurl:admin/message/search.php'}] [1, 2]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include:

  • Replace the affected product with an alternative solution if possible.
  • Implement prepared statements with parameter binding to separate SQL code from user input.
  • Apply strict input validation and filtering to ensure inputs conform to expected formats.
  • Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts like root or admin.
  • Conduct regular security audits to detect and remediate vulnerabilities promptly.

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