CVE-2025-8947
BaseFortify
Publication date: 2025-08-14
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 |
|---|---|---|
| projectworlds | visitor_management_system | 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?
CVE-2025-8947 is a critical SQL injection vulnerability in Projectworlds Visitor Management System version 1.0, specifically in the '/query_data.php' file. It arises from improper handling and insufficient validation of the 'dateF' and 'dateP' parameters, which are used directly in SQL queries without proper sanitization. This flaw allows attackers to inject malicious SQL code remotely without authentication, enabling unauthorized database access, data leakage, data modification or deletion, full system control, and potential service disruption. Multiple SQL injection techniques such as boolean-based blind, error-based, and time-based blind injections have been demonstrated to exploit this vulnerability. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive data, modification or deletion of data, full system compromise, and disruption of services. Attackers can exploit the flaw remotely without authentication, potentially gaining control over the system and compromising confidentiality, integrity, and availability of the affected system. [1, 2, 3, 4, 5]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the '/query_data.php' endpoint for SQL injection flaws in the 'dateF' and 'dateP' POST parameters. Using tools like sqlmap to perform time-based blind SQL injection tests is effective. Example payloads include injecting SQL code that causes delayed responses, such as using the MySQL SLEEP function. A sample sqlmap command to test the 'dateF' parameter could be: sqlmap -u "http://target.com/query_data.php" --data="dateF=2025-08-06" --method=POST --time-sec=5 --technique=T Similarly, testing the 'dateP' parameter with analogous payloads is recommended. Monitoring for unusual delays or error messages in responses can also indicate exploitation attempts. [1, 2]
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 to ensure 'dateF' and 'dateP' parameters conform to expected formats. - Minimizing database user permissions by avoiding use of high-privilege accounts for application database access. - Conducting regular security audits to detect and address vulnerabilities promptly. - If possible, replacing or updating the affected software to a version without this vulnerability. These measures help prevent SQL injection exploitation and protect database integrity and confidentiality. [1, 2]