# CVE-2025-23913: WordPress Google Map Professional Plugin <= 1.0 - SQL Injection vulnerability

> An attacker can exploit SQL injection in the Google Map Professional plugin to read or modify database contents.

- **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:** 16 Jan 2025
- **Updated:** 11 May 2026
- **Also known as:** GHSA-3c5g-f95f-fq26

## What is CVE-2025-23913?

CVE-2025-23913 is a high-severity SQL injection vulnerability in pankajpragma WordPress Google Map Professional, published on 16 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in pankajpragma WordPress Google Map Professional google-map-professional allows SQL Injection.This issue affects WordPress Google Map Professional: from n/a through <= 1.0.

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

## Which versions are affected by CVE-2025-23913?


## How do I fix CVE-2025-23913?

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

## Is CVE-2025-23913 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-23913 and fix it if it is affected.

What it is: CVE-2025-23913 is a high-severity SQL injection vulnerability in pankajpragma WordPress Google Map Professional, published on 16 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-23913 in the wild and no public exploit code.

Affected product: pankajpragma WordPress Google Map Professional. 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-2025-23913/ (Markdown: https://insights.sbomify.com/CVE-2025-23913/index.md)
```

## Sources

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

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