CVE-2025-57104
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-09-20
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| zeon | teampel | 5.1.6 |
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
Can you explain this vulnerability to me?
CVE-2025-57104 is an SQL injection vulnerability in Teampel version 5.1.6, specifically in the /Common/login.aspx page. An attacker can inject malicious SQL code into a user input field, such as the password field, to manipulate the SQL query. For example, using a payload like `-1' OR 1=1 AND 1=1 --` allows the attacker to bypass authentication controls and gain unauthorized access to the backend system. [1]
How can this vulnerability impact me? :
This vulnerability can allow an attacker to bypass authentication and gain unauthorized access to the backend system. This unauthorized access could lead to data breaches, manipulation or theft of sensitive information, and potential control over the affected system. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /Common/login.aspx input fields for SQL injection. For example, you can attempt to input the payload `-1' OR 1=1 AND 1=1 --` in the username or password fields to see if authentication is bypassed. Network monitoring tools can also look for such suspicious payloads in HTTP requests targeting /Common/login.aspx. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling or restricting access to the /Common/login.aspx page, applying input validation and parameterized queries to prevent SQL injection, and monitoring for suspicious login attempts using payloads like `-1' OR 1=1 AND 1=1 --`. If a patch or update for Teampel 5.1.6 is available, apply it promptly to fix the vulnerability. [1]