CVE-2019-25335
BaseFortify
Publication date: 2026-02-12
Last updated on: 2026-02-13
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| websitem | pro-7070 | 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability exists in PRO-7070 HazΔ±r Profesyonel Web Sitesi version 1.0 and is an authentication bypass issue in the administration panel login page.
Attackers can exploit this vulnerability by entering '=' or 'or' as both the username and password, which allows them to bypass the authentication mechanism.
This means unauthorized users can gain access to the administrative interface without valid credentials.
How can this vulnerability impact me? :
This vulnerability can allow attackers to gain unauthorized access to the administrative interface of the affected web application.
Such unauthorized access can lead to potential misuse or manipulation of administrative functions, which may compromise the security and integrity of the website.
According to the CVSS v3.1 score of 7.5, the impact on confidentiality is high, indicating that sensitive information could be exposed.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know