CVE-2025-8467
BaseFortify
Publication date: 2025-08-02
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 | wazifa_system | 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-8467 is a critical SQL injection vulnerability in version 1.0 of the Wazifa System, specifically in the /controllers/regcontrol.php file. It occurs because the application does not properly validate or sanitize the 'username' parameter, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, letting attackers retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to your database, leakage of sensitive information, modification or deletion of data, potential system takeover, and disruption of services. It threatens the confidentiality, integrity, and availability of your system 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 checking for the presence of the vulnerable file /controllers/regcontrol.php in the Wazifa System 1.0 and by testing the 'username' parameter for SQL injection. One method is to use Google dorking with the query `inurl:controllers/regcontrol.php` to identify potentially vulnerable targets. Additionally, manual or automated SQL injection testing tools can be used to send crafted payloads to the 'username' parameter and observe if SQL errors or unexpected behavior occur. Specific commands might include using curl or sqlmap to test the parameter, for example: `sqlmap -u "http://target/controllers/regcontrol.php?username=test" --risk=3 --level=5` to automate detection of SQL injection vulnerabilities. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements (parameterized queries) to ensure user inputs like 'username' are treated as data and not executable SQL code. 2) Applying strict input validation and filtering on the 'username' parameter to allow only expected input formats. 3) Minimizing database user permissions by restricting the database account used by the application to only necessary privileges, avoiding use of high-privilege accounts such as 'root' or 'admin'. 4) Conducting regular security audits of the code and system to detect and fix vulnerabilities promptly. If possible, replacing the affected component with a secure alternative is recommended. [2, 3]