CVE-2025-8923
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-8923 is a critical SQL injection vulnerability in the Job Diary 1.0 application, specifically in the /edit-details.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, allowing attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data modification or deletion, and potentially full system compromise. Attackers can exploit it remotely without authentication, which may result in service disruption and loss of data integrity and confidentiality, posing significant risks to system security and business continuity. [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 /edit-details.php endpoint with specially crafted SQL injection payloads targeting the 'id' parameter. Example commands include using sqlmap against the URL: sqlmap -u "http://<target>/job-diary-master/edit-details.php?id=1" --risk=3 --level=5 to automate detection. Manual testing can involve sending HTTP GET requests with payloads such as: id=(SELECT (CASE WHEN (5391=5391) THEN 1 ELSE (SELECT 8065 UNION SELECT 8716) END)) (boolean-based), id=1 OR (SELECT 4303 FROM(SELECT COUNT(*),CONCAT(0x71716b7071,(SELECT (ELT(4303=4303,1))),0x7162787071,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a) (error-based), id=1 AND (SELECT 8492 FROM (SELECT(SLEEP(5)))dxPM) (time-based), or UNION-based injections. Additionally, Google dorking with queries like "inurl:edit-details.php" can help locate vulnerable instances. [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 such as 'root' or 'admin' for routine database operations. Conducting regular security audits to identify and remediate vulnerabilities promptly is also recommended. If possible, replacing the affected software with a secure alternative is advised. [2, 3]