CVE-2025-10790
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 |
|---|---|---|
| oretnom23 | simple_forum\/discussion_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-10790 is a critical SQL injection vulnerability in the Simple Forum Discussion System V1.0, specifically in the 'save_category' function within admin_class.php. The vulnerability occurs because the 'description' parameter is directly used in SQL queries without proper input validation or sanitization. This allows attackers to inject malicious SQL code remotely, enabling unauthorized manipulation of database queries. It is a time-based blind SQL injection affecting MySQL databases. [1]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, leakage of sensitive data, data tampering, full system control by attackers, and potential service disruption. These impacts pose significant risks to system security and business continuity. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'description' parameter in the /ajax.php?action=save_category endpoint for SQL injection, specifically using time-based blind SQL injection techniques. A proof-of-concept involves injecting a payload that causes the database to execute a SLEEP(5) command, which delays the response if the injection is successful. Automated tools like sqlmap can be used to test this vulnerability. For example, using sqlmap targeting the vulnerable parameter can confirm the presence of the SQL injection. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'description' parameter, minimizing database user permissions by avoiding high-privilege accounts for routine operations, and conducting regular security audits to detect and address vulnerabilities promptly. [1]