CVE-2019-25459
Multiple SQL Injection Vulnerabilities in Web Ofisi Emlak V2 Endpoint
Publication date: 2026-02-22
Last updated on: 2026-03-02
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| web-ofisi | emlak | 2.0.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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized access to sensitive database information. Attackers can extract confidential data stored in the database without authentication.
Additionally, attackers can perform time-based blind SQL injection attacks to infer data indirectly, potentially leading to further exploitation or data leakage.
The vulnerability has a high severity score (CVSS v3.1 Base Score 8.2) indicating a significant risk, with high confidentiality impact and low integrity impact.
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': "The vulnerability in Web Ofisi Emlak V2 is a set of multiple SQL injection flaws in the web application's search endpoint. These flaws allow unauthenticated attackers to inject malicious SQL code into various GET parameters such as emlak_durumu, emlak_tipi, il, ilce, kelime, and semt."}, {'type': 'paragraph', 'content': 'By exploiting these injection points, attackers can manipulate the database queries executed by the application. This can lead to unauthorized extraction of sensitive information from the database or performing time-based blind SQL injection attacks to infer data.'}] [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability can be detected by testing the vulnerable GET parameters of the Web Ofisi Emlak V2 application for SQL injection using crafted payloads.'}, {'type': 'list_item', 'content': "Use boolean-based SQL injection payloads on parameters like emlak_durumu, ilce, kelime, and semt. Example payload: -1' OR 3*2*1=6 AND 000397=000397 --"}, {'type': 'list_item', 'content': "Use time-based blind SQL injection payloads on parameters like emlak_tipi and il. Example payload: 0'XOR(if(now()=sysdate(),sleep(0),0))XOR'Z"}, {'type': 'paragraph', 'content': 'These payloads can be tested by sending HTTP GET requests to the vulnerable endpoint (e.g., emlak-ara.html) with the parameters set to the payloads and observing the response behavior or response time delays.'}, {'type': 'paragraph', 'content': 'Example command using curl to test boolean-based SQL injection on emlak_durumu parameter:'}, {'type': 'list_item', 'content': 'curl "http://targetsite/emlak-ara.html?emlak_durumu=-1\'%20OR%203*2*1=6%20AND%20000744=000744--"'}, {'type': 'paragraph', 'content': 'Example command using curl to test time-based blind SQL injection on emlak_tipi parameter:'}, {'type': 'list_item', 'content': 'curl "http://targetsite/emlak-ara.html?emlak_tipi=0\'%20XOR(if(now()=sysdate(),sleep(5),0))XOR\'Z"'}] [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Sanitize and validate all user inputs, especially GET parameters such as emlak_durumu, emlak_tipi, il, ilce, kelime, and semt, to prevent SQL injection.
- Use prepared statements with parameterized queries instead of directly embedding user input into SQL queries.
- Apply the latest patches or updates from the vendor if available.
- Restrict database user permissions to limit the impact of a potential SQL injection attack.
- Implement Web Application Firewall (WAF) rules to detect and block SQL injection attempts.