CVE-2025-11102
BaseFortify
Publication date: 2025-09-28
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-11102 is a critical SQL injection vulnerability in Campcodes Online Learning Management System version 1.0, specifically in the file /admin/edit_content.php. It occurs because the 'Title' parameter is not properly sanitized, allowing attackers to inject malicious SQL code. This flaw enables unauthorized access to the database and manipulation of data. The attack can be performed remotely without authentication, making it easy to exploit. [1, 2]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, modification or deletion of data, and potentially full system compromise or service disruption. Attackers can exploit it remotely without authentication, which puts the confidentiality, integrity, and availability of the system at risk. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the `title` parameter in POST requests to the `/admin/edit_content.php` file for SQL injection. You can use SQL injection testing tools like sqlmap to automate detection. Manual testing can involve sending payloads such as Boolean-based blind SQL injection using the RLIKE operator or time-based blind SQL injection using the SLEEP function. Example payloads include: Boolean-based: ``` title=11' RLIKE (SELECT (CASE WHEN (6035=6035) THEN 11 ELSE 0x28 END)) AND 'tjJZ'='tjJZ ``` Time-based: ``` title=11' AND (SELECT 3600 FROM (SELECT(SLEEP(5)))WjSV) AND 'Yhzo'='Yhzo ``` Using sqlmap, a command might be: ``` sqlmap -u "http://target/admin/edit_content.php" --data="title=11" --risk=3 --level=5 ``` This will test the `title` parameter for SQL injection vulnerabilities. [2, 1]
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. - Enforce strict input validation and filtering on the `title` parameter to ensure it conforms to expected formats. - Minimize database user permissions by avoiding use of high-privilege accounts (e.g., root or admin) for the application database connection. - Conduct regular security audits to detect and address vulnerabilities promptly. - Consider replacing the affected software with an alternative product if possible, as no known mitigations are documented. These steps help prevent exploitation and protect system security and data integrity. [2, 1]