# CVE-2026-127217: Post to Google My Business WordPress Plugin < 3.5.7 SSRF via Preview REST Route


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-2pmq-jg8m-f7px

## What is CVE-2026-127217?

CVE-2026-127217 is a medium-severity vulnerability in Koen Reus Post to Google My Business (Google Business Profile), published on 13 Nov 2026. 

### Official description

Post to Google My Business plugin for WordPress before 3.5.7 contains a blind server-side request forgery vulnerability that allows authenticated users with Contributor-level privileges or higher to make the server send requests to arbitrary hosts by supplying an unvalidated mbp_post_attachment URL that reaches a raw getimagesize() call in validate_external_image_size() via the preview REST route. Attackers can exploit this to perform internal port scanning, probe internal-only services and cloud metadata endpoints, and trigger GET-based side effects on internal systems, bypassing network perimeter controls since the request originates from the web server.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-127217 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-127217 is a medium-severity vulnerability in Koen Reus Post to Google My Business (Google Business Profile), published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-127217 in the wild and no public exploit code.

Affected product: Koen Reus Post to Google My Business (Google Business Profile). 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-127217/ (Markdown: https://insights.sbomify.com/CVE-2026-127217/index.md)
```

## Sources

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

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