# CVE-2019-25753: Joomla! Component VMap 1.9.6 SQL Injection via loadmarker

> Unauthenticated attackers can execute arbitrary SQL queries via the latlngbound parameter in the VMap plugin to extract sensitive database information.

- **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:** 19 Jun 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-xqfp-43p8-62jx

## What is CVE-2019-25753?

CVE-2019-25753 is a high-severity SQL injection vulnerability in Wdmtech VMap, published on 19 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Joomla! Component VMap 1.9.6 contains an SQL injection vulnerability that allows unauthenticated attackers to execute arbitrary SQL queries by injecting malicious code into the latlngbound parameter. Attackers can send GET requests to index.php with the option=com_vmap&task=loadmarker parameters containing SQL injection payloads to manipulate database queries and extract sensitive information.

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

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

It affects 1 product.


Products: Wdmtech Vmap.

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

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

## Is CVE-2019-25753 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-25753 is a high-severity SQL injection vulnerability in Wdmtech VMap, published on 19 Jun 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-25753 exists.

Affected product: Wdmtech VMap. 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-25753/ (Markdown: https://insights.sbomify.com/CVE-2019-25753/index.md)
```

## Sources

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

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