CVE-2025-10033
BaseFortify
Publication date: 2025-09-06
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 |
|---|---|---|
| emiloimagtolis | online_discussion_forum | 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-10033 is a critical SQL injection vulnerability in the Itsoucecode Online Discussion Forum version 1.0, specifically in the /admin file. It occurs because the 'username' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized manipulation of database queries, such as retrieving, modifying, or deleting sensitive data. The vulnerability can be exploited remotely without authentication, making it highly accessible. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, allowing attackers to retrieve sensitive information, modify or delete data, and potentially gain full control over the system. It can also cause service disruption. Since no authentication is required, attackers can easily exploit this flaw remotely, posing a significant risk to confidentiality, integrity, and availability of the system. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /admin endpoint for SQL injection in the 'username' parameter. A common method is to send specially crafted POST requests that include SQL injection payloads, such as time-based blind SQL injection payloads. For example, sending a POST request with the parameter: username=111' AND (SELECT 7039 FROM (SELECT(SLEEP(5)))ZzzA) AND 'tiTj'='tiTj&password=222 can confirm the vulnerability if the response is delayed. Tools like sqlmap can automate this detection by targeting the URL with the vulnerable parameter. Example command using sqlmap: sqlmap -u "http://target/admin" --data="username=111&password=222" --technique=T --level=5 --risk=3 [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Apply strict input validation and filtering on the 'username' parameter to ensure it conforms to expected formats. 3) Minimize database user permissions by avoiding use of high-privilege accounts for routine operations. 4) Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly. If possible, replace the affected software with an alternative product as no known countermeasures exist. Applying these fixes immediately is critical to maintain system security and data integrity. [2, 3]