CVE-2025-8948
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-8948 is a critical SQL injection vulnerability in the projectworlds Visitor Management System version 1.0, specifically in the /front.php file. The vulnerability arises from improper handling and inadequate validation of the 'rid' parameter, which is used directly in SQL queries without proper sanitization. This allows attackers to inject malicious SQL code remotely without authentication, potentially leading to unauthorized database access, data leakage, data tampering, and full system compromise. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, exposure and leakage of sensitive data, unauthorized modification or deletion of data, potential full system control by attackers, and disruption of service. Since exploitation does not require authentication and a public proof-of-concept exploit exists, attackers can easily exploit this flaw to compromise 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 'rid' parameter in the /front.php file for SQL injection. You can use tools like sqlmap to automate detection. Example sqlmap command: sqlmap -u "http://target.com/front.php?rid=111" --batch --dbs. Additionally, manual testing can be done using payloads such as error-based or time-based SQL injection strings in the 'rid' parameter, for example: rid=111'||(SELECT 0x4c58567a WHERE 8335=8335 AND (SELECT 3715 FROM(SELECT COUNT(*),CONCAT(0x716a716271,(SELECT (ELT(3715=3715,1))),0x7162627671,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a))||'&logout=Checkout or rid=111'||(SELECT 0x58646164 WHERE 2767=2767 AND (SELECT 1791 FROM (SELECT(SLEEP(5)))KrQP))||'&logout=Checkout to observe error messages or response delays indicating injection. [1]
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 all user inputs including the 'rid' parameter, and minimizing database user permissions by avoiding high-privilege accounts for the application. Regular security audits should be conducted to detect and remediate vulnerabilities promptly. Since no known mitigations exist for this specific vulnerability, replacing the affected software with an alternative product is also recommended to avoid exploitation. [1, 2]