CVE-2025-6890
BaseFortify
Publication date: 2025-06-30
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 |
|---|---|---|
| carmelo | movie_ticketing_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-6890 is a critical SQL injection vulnerability in the Movie Ticketing System version 1.0, specifically in the /ticketConfirmation.php file. It occurs because the 'date' parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code, potentially enabling unauthorized access to the database, modification or deletion of data, and retrieval of sensitive information. The vulnerability can be exploited remotely and a public proof-of-concept exploit is available. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized database access, data leakage, data tampering, full system compromise, and service disruption. Attackers can modify or delete data and retrieve sensitive information. This poses a significant threat to system security and business continuity if not remediated promptly. [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 '/ticketConfirmation.php' endpoint and testing the 'date' parameter for SQL injection. One detection method is to use web application scanning tools or manual testing with SQL injection payloads on the 'date' parameter in POST requests. Additionally, Google Dorking can be used to identify vulnerable targets by searching for "inurl:ticketConfirmation.php". Example commands include using curl to send a POST request with a test SQL injection payload, e.g., curl -X POST -d "date=' OR '1'='1" https://targetsite.com/ticketConfirmation.php, or using sqlmap to automate detection: sqlmap -u "https://targetsite.com/ticketConfirmation.php" --data="date=2025-06-30" --risk=3 --level=5. Monitoring for unusual database errors or logs indicating SQL errors related to the 'date' parameter can also help detect exploitation attempts. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to ensure that user input in the 'date' parameter is not directly included in SQL queries. 2) Applying strict input validation and filtering to ensure the 'date' parameter conforms to expected formats. 3) Minimizing database user permissions by avoiding the use of high-privilege accounts for routine database operations. 4) Conducting regular security audits and code reviews to detect and remediate vulnerabilities promptly. If possible, replace or update the affected component to a version without this vulnerability. These steps help prevent SQL injection exploitation and protect the system's confidentiality, integrity, and availability. [2]