CVE-2025-10800
BaseFortify
Publication date: 2025-09-22
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 |
|---|---|---|
| emiloi | 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-10800 is a critical SQL injection vulnerability in version 1.0 of the Online Discussion Forum Project, specifically in the /index.php file. It arises from improper handling of the email and password parameters, which are used directly in SQL queries without proper input validation or sanitization. Attackers can exploit this remotely without authentication by injecting malicious SQL code via these parameters, allowing unauthorized database access, data leakage, data modification or deletion, full system compromise, and potential service disruption. [1, 2]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive information, modification or deletion of data, full system compromise, and disruption of services. Exploitation requires no authentication and can be performed remotely, posing a significant threat to system security and business continuity. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by performing time-based blind SQL injection tests targeting the 'email' and 'password' POST parameters in the /index.php file. A proof-of-concept payload uses a delay function such as MySQL's SLEEP to confirm the vulnerability, for example: email=111&password=111111' AND (SELECT 2454 FROM (SELECT(SLEEP(5)))tCKO) AND 'lDwk'='lDwk. Tools like sqlmap can be used to automate detection by sending crafted requests to the target URL and observing response delays. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to separate SQL code from user input, preventing injection; 2) Enforcing strict input validation and filtering to ensure inputs conform to expected formats; 3) Minimizing database user permissions by avoiding high-privilege accounts such as 'root' or 'admin' for routine operations; 4) Conducting regular security audits to detect and address vulnerabilities promptly. [1, 2]