CVE-2025-7533
BaseFortify
Publication date: 2025-07-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-7533 is a critical SQL injection vulnerability in the Job Diary 1.0 application, specifically in the /view-details.php file. It occurs because the 'job_id' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, potentially allowing attackers to view, 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 gain unauthorized access to your database. They can view, modify, or delete sensitive information, potentially leading to data leakage, data corruption, full system compromise, and service disruption. Since the exploit requires no authentication and can be triggered remotely, it poses a high risk 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 'job_id' parameter in the /view-details.php file for SQL injection. Tools like sqlmap can be used to automate detection. Example sqlmap command: sqlmap -u "http://target/view-details.php?job_id=1" --batch --level=5 --risk=3. Additionally, manual testing with payloads such as 'job_id=1' AND 1=1 -- and 'job_id=1' AND 1=2 -- can help identify SQL injection. Searching for URLs containing 'view-details.php' using Google Hacking techniques can help identify 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 prevent SQL injection, enforcing strict input validation and filtering on the 'job_id' parameter, minimizing database user privileges by avoiding high-privilege accounts for the application database connection, and conducting regular security audits. If possible, replacing the affected component with an alternative product is recommended as no known mitigations are documented. [2, 3]