CVE-2025-8921
BaseFortify
Publication date: 2025-08-13
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 |
|---|---|---|
| anisha | job_diary | 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-8921 is a critical SQL injection vulnerability in the Job Diary 1.0 application, specifically in the /user-apply.php file. It occurs because the 'job_title' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL commands. This enables unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing attackers to remotely execute arbitrary SQL commands on your database without any authentication. They can extract sensitive information, modify or delete data, gain full control over the system, and potentially disrupt services. This compromises the confidentiality, integrity, and availability of your system and data. [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 'job_title' parameter in the /user-apply.php file for SQL injection. One effective method is to use the sqlmap tool with a boolean-based blind SQL injection payload targeting the 'job_title' parameter in a multipart POST request. Additionally, attackers may be identified by scanning for the URL pattern 'inurl:user-apply.php' using Google dorking to find vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, enforcing strict input validation and filtering on the 'job_title' parameter, and limiting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. It is also recommended to conduct regular security audits of code and systems. If possible, replacing the affected software with an alternative product is suggested. [2, 3, 1]