CVE-2025-5650
BaseFortify
Publication date: 2025-06-05
Last updated on: 2025-06-10
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| 1000projects | online_notice_board | 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-5650 is a critical SQL injection vulnerability in version 1.0 of the 1000projects Online Notice Board software, specifically in the /register.php file. It occurs due to improper handling of the 'fname' parameter, which is used directly in SQL queries without proper input validation or sanitization. This allows attackers to inject malicious SQL code remotely without authentication, potentially compromising the confidentiality, integrity, and availability of the system. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, full system control by attackers, and potential service disruption. Exploitation requires no authentication and is easy to perform, which makes it a serious threat to system security and business continuity if left unaddressed. [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 /register.php endpoint for SQL injection on the 'fname' parameter. A common method is to use a time-based blind SQL injection payload such as: fname=1' AND (SELECT 3399 FROM (SELECT(SLEEP(5)))KZRF) AND 'ZfhA'='ZfhA to observe delayed responses indicating vulnerability. Tools like sqlmap can be used to automate detection by targeting the 'fname' parameter with POST data. Additionally, Google dorking with queries like "inurl:register.php" can help identify potentially vulnerable targets. [1, 2, 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 inputs, preventing injection. 2) Enforce strict input validation and filtering to ensure inputs conform to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as root or admin 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. [1, 2, 3]