CVE-2025-8164
BaseFortify
Publication date: 2025-07-25
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 |
|---|---|---|
| fabian | public_chat_room | 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-8164 is a critical SQL injection vulnerability in the send_message.php file of code-projects Public Chat Room 1.0. It occurs because the 'id' parameter from user input is directly concatenated into SQL queries without proper escaping or use of parameterized queries. This allows attackers to inject malicious SQL code remotely, which can manipulate the database, bypass authentication, and retrieve sensitive information. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including bypassing authentication, accessing sensitive database information, tampering with data, gaining full system control, and causing service interruptions. Exploitation does not require any login or authorization, making it easier for attackers to compromise the system remotely. [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 'id' POST parameter in the send_message.php file for SQL injection. Tools like sqlmap can be used to automate detection by sending crafted POST requests targeting the 'id' parameter. Additionally, manual testing can include injecting SQL payloads such as boolean-based blind injections (e.g., using MySQL RLIKE operator), error-based injections, or time-based blind injections (e.g., using MySQL SLEEP function) to observe responses. A sample sqlmap command could be: sqlmap -u "http://target/send_message.php" --data="id=1" --risk=3 --level=5 --batch [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent direct concatenation of user input into SQL queries. Additionally, apply strict input validation and filtering to ensure the 'id' parameter conforms to expected formats. Conduct regular security audits to identify and remediate vulnerabilities promptly. If possible, replace the affected software with a secure alternative or update the code to fix the SQL injection flaw. [2, 3]