CVE-2025-11090
BaseFortify
Publication date: 2025-09-28
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 |
|---|---|---|
| angeljudesuarez | open_source_job_portal | 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-11090 is a critical SQL injection vulnerability in itsourcecode Open Source Job Portal version 1.0. It occurs in the file /admin/employee/index.php when handling the 'id' parameter with the 'view=edit' argument. Due to insufficient validation and sanitization of this 'id' parameter, attackers can inject malicious SQL queries remotely without authentication. This allows unauthorized access to the database, enabling attackers to retrieve, modify, or delete sensitive data. [1, 2, 4]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing attackers to perform unauthorized database access, leading to data leakage, modification, or deletion. It can result in full system compromise and potential service disruption, threatening system security and business continuity. The exploit is publicly available and easy to use, increasing the risk of exploitation. [1, 2, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the vulnerable URL parameter with SQL injection payloads. For example, using the sqlmap tool against the URL http://<target>/jobportal/admin/employee/index.php?view=edit&id=2018001 can confirm the vulnerability. Example sqlmap command: sqlmap -u "http://<target>/jobportal/admin/employee/index.php?view=edit&id=2018001" --batch --dbs. Additionally, manual testing with payloads such as ' AND 1=1-- or ' UNION SELECT NULL,NULL,...-- can be used to detect injection points. [4]
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. 2) Apply strict input validation and filtering to ensure the 'id' parameter only accepts expected formats (e.g., numeric). 3) Minimize database user permissions by avoiding high-privilege accounts for routine operations. 4) Conduct regular security audits to detect and fix vulnerabilities promptly. Since no known countermeasures or patches are available, replacing the affected product with a secure alternative is also suggested. [2, 4]