# CVE-2026-48967: WordPress Geo Mashup plugin <= 1.13.19 - SQL Injection vulnerability

> A SQL injection vulnerability in the Geo Mashup WordPress plugin allows subscribers to execute arbitrary SQL commands, potentially compromising database integrity and confidentiality.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2026
- **Updated:** 17 Jun 2026
- **Also known as:** GHSA-657f-hp84-rfhg

## What is CVE-2026-48967?

CVE-2026-48967 is a high-severity SQL injection vulnerability in Dylan Kuhn Geo Mashup, published on 17 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Subscriber SQL Injection in  Geo Mashup <= 1.13.19 versions.

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

## Which versions are affected by CVE-2026-48967?


## How do I fix CVE-2026-48967?

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

## Is CVE-2026-48967 being exploited?

There is no known exploitation of CVE-2026-48967 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48967 and fix it if it is affected.

What it is: CVE-2026-48967 is a high-severity SQL injection vulnerability in Dylan Kuhn Geo Mashup, published on 17 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48967 in the wild and no public exploit code.

Affected product: Dylan Kuhn Geo Mashup. 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-2026-48967/ (Markdown: https://insights.sbomify.com/CVE-2026-48967/index.md)
```

## Sources

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

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