CVE-2025-11584
BaseFortify
Publication date: 2025-10-10
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 |
|---|---|---|
| fabian | online_job_search_engine | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-11584 is a critical SQL injection vulnerability in the Online Job Search Engine version 1.0, specifically in the /searchjob.php file. It occurs because the application does not properly validate or sanitize the 'txtspecialization' input parameter, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, potentially leading to data leakage, modification, deletion, or even full system compromise. The vulnerability can be exploited remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, modification or deletion of database records, and disruption of service. Attackers can exploit it remotely without authentication to manipulate SQL queries, compromising the confidentiality, integrity, and availability of the system. This may lead to data breaches, loss of business continuity, and potential full system compromise. [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 /onlineJobSearchEngine/searchjob.php endpoint for SQL injection via the txtspecialization parameter. You can use tools like sqlmap to automate detection by sending crafted POST requests with manipulated txtspecialization values. Example commands include using sqlmap with a POST request targeting the vulnerable parameter. Additionally, manual testing can be done using payloads such as txtspecialization=-5138' OR 3002=3002 # for boolean-based blind SQL injection or txtspecialization=1' AND (SELECT SLEEP(5)) for time-based blind SQL injection to observe changes in response behavior. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Using prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Implementing strict input validation and filtering to ensure inputs conform to expected formats. 3) Limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. 4) Conducting regular security audits of code and systems to detect and fix vulnerabilities promptly. If possible, replacing the affected software with an alternative product is also suggested. [1, 2, 3]