# CVE-2026-15381: WP Go Maps < 10.1.04 - Unauthenticated SQL Injection via Markers REST filter

> Unauthenticated attackers can execute SQL injection attacks via the Markers REST filter in WP Go Maps, potentially reading or modifying database contents.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-55gh-xjv7-5vwp

## What is CVE-2026-15381?

CVE-2026-15381 is a low-severity SQL injection vulnerability in Unknown WP Go Maps, published on 31 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Go Maps  WordPress plugin before 10.1.04 does not properly sanitise and escape a parameter before using it in a SQL query, allowing unauthenticated users to perform SQL injection attacks.

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

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


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

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

## Is CVE-2026-15381 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15381 is a low-severity SQL injection vulnerability in Unknown WP Go Maps, published on 31 Jul 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-2026-15381 exists.

Affected product: Unknown WP Go Maps. 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-15381/ (Markdown: https://insights.sbomify.com/CVE-2026-15381/index.md)
```

## Sources

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

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