CVE-2018-25362
BaseFortify
Publication date: 2026-05-25
Last updated on: 2026-05-25
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
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. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows attackers to extract sensitive database information including usernames, passwords, and database credentials through SQL injection. This exposure of sensitive personal data can lead to non-compliance with data protection regulations such as GDPR and HIPAA, which require the protection of personal and sensitive information from unauthorized access.
Specifically, the compromise of usernames and passwords can violate confidentiality requirements, potentially leading to breaches of user privacy and data security mandates under these regulations.
Can you explain this vulnerability to me?
The vulnerability in Twitter-Clone 1 is a SQL injection found in the follow.php file. It occurs because the userid parameter is not properly sanitized, allowing attackers to inject malicious SQL code.
Attackers can use union-based or time-based blind SQL injection techniques to manipulate database queries and extract sensitive information such as usernames, passwords, and database credentials.
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized access to sensitive user data stored in the database.
- Attackers can steal usernames and passwords.
- Database credentials can be exposed, potentially allowing further compromise of the system.
- The integrity and confidentiality of the database can be severely compromised.