CVE-2025-8922
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-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?
This vulnerability is a critical SQL injection flaw in the Job Diary version 1.0 software, specifically in the /admin-inbox.php file. It occurs because the 'id' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, letting attackers view, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized access to your database, resulting in data leakage, modification, or deletion. Attackers can compromise the integrity and availability of your system, potentially causing full system compromise and service disruption. Since no authentication is required, the attack can be initiated remotely with ease. [1, 2, 3]
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 'id' parameter in the /admin-inbox.php file for SQL injection flaws. Tools like sqlmap can be used to automate detection. For example, running sqlmap against the URL: http://<target>/job-diary-master/admin-inbox.php?id=1 can help identify the vulnerability. Manual testing can include boolean-based blind injections, error-based injections using MySQL functions like FLOOR and RAND, and time-based blind injections using SLEEP to observe delays. Additionally, searching for the vulnerable endpoint using Google dorking with queries like "inurl:admin-inbox.php" can help identify exposed targets. [2, 3]
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 'id' parameter, and minimizing database user privileges by avoiding high-privilege accounts for routine operations. It is also recommended to conduct regular security audits of the code and system. Since no known mitigations or countermeasures are documented, replacing the affected software with an alternative product is advised to secure the system and maintain data integrity. [1, 2, 3]