CVE-2025-9763
BaseFortify
Publication date: 2025-09-01
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 |
|---|---|---|
| campcodes | online_learning_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
Can you explain this vulnerability to me?
CVE-2025-9763 is a critical SQL injection vulnerability in Campcodes Online Learning Management System version 1.0, specifically in the /student_signup.php file. The vulnerability occurs because the 'username' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized manipulation of the database, such as retrieving, modifying, or deleting data. The attack can be launched remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized database access, data leakage, data tampering, and potential full system control. Attackers can modify or delete sensitive information, disrupt services, and compromise system security and business continuity. Since no authentication is required, the risk is significant and immediate remediation is necessary to protect data integrity and system availability. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the /lms/student_signup.php endpoint with specially crafted payloads targeting the 'username' parameter. Common detection methods include using SQL injection testing tools like sqlmap against the vulnerable URL with POST data containing injection payloads. Example payloads include boolean-based, error-based, and time-based SQL injection strings such as: - Boolean-based: username=123123' OR NOT 1377=1377 # - Error-based: username=123123' OR (SELECT 9592 FROM(SELECT COUNT(*),CONCAT(0x7176706a71,(SELECT (ELT(9592=9592,1))),0x7176706b71,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)-- mIET - Time-based: username=123123' AND (SELECT 5985 FROM (SELECT(SLEEP(5)))QjGp)-- paGb A sample sqlmap command to test the vulnerability is: sqlmap -u "http://<target-ip>/lms/student_signup.php" --data="username=anything&otherparam=value" --method=POST --batch Additionally, Google dorking with queries like inurl:student_signup.php can help identify potentially vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. - Enforce strict input validation and filtering on the 'username' parameter to ensure only expected data formats are accepted. - Minimize database user permissions by avoiding use of high-privilege accounts (e.g., root or admin) for routine database operations. - Conduct regular security audits of code and systems to detect and address vulnerabilities promptly. Since no fixed version is available, these code-level mitigations are critical to secure the system and maintain data integrity. [2]