# CVE-2019-25456: Web Ofisi Emlak v2 SQL Injection via ara Parameter

> Unauthenticated attackers can inject SQL via the 'ara' parameter to extract database information or cause denial of service in Web Ofisi Emlak.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Feb 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-wf2x-4p8v-p7m6

## What is CVE-2019-25456?

CVE-2019-25456 is a high-severity SQL injection vulnerability in Web-ofisi Emlak, published on 22 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Web Ofisi Emlak v2 contains an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through the 'ara' GET parameter. Attackers can send requests to with time-based SQL injection payloads to extract sensitive database information or cause denial of service.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2019-25456?

It affects 1 product.


Products: Web-Ofisi Emlak.

## How do I fix CVE-2019-25456?

No fix has been published for CVE-2019-25456 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-25456 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25456 exists.

## Other vulnerabilities in Web-ofisi Emlak

- [CVE-2019-25459](https://insights.sbomify.com/CVE-2019-25459/): Web Ofisi Emlak V2 SQL Injection via emlak-ara.html (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25456 and fix it if it is affected.

What it is: CVE-2019-25456 is a high-severity SQL injection vulnerability in Web-ofisi Emlak, published on 22 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25456 exists.

Affected product: Web-ofisi Emlak. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-25456/ (Markdown: https://insights.sbomify.com/CVE-2019-25456/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-25456
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-25456
- OSV: https://osv.dev/vulnerability/CVE-2019-25456

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-25456/
Summaries are generated and may contain mistakes; the official description above is the record.
