CVE-2026-127217 · Package
NO FIX YET · SEE WHAT TO DO
The Post to Google My Business plugin for WordPress, before 3.5.7, lets an authenticated Contributor-level user make the server send requests to arbitrary hosts through an unvalidated image URL. An attacker can use this to scan internal networks, reach internal services and cloud metadata endpoints, and trigger GET requests on internal systems.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Sites running the Post to Google My Business plugin for WordPress before 3.5.7 that let Contributor-level or higher users create content are exposed. The flaw sits in the preview REST route, so the server making outbound requests is the one that matters. Sites without this plugin, or with it at 3.5.7 or later, can skip it.
Not affected if no-contributor-users, plugin-not-installed, version-3.5.7-or-later
Who cares self-hosted, wordpress
wp-content/plugins/ on the server3.5.73.5.7 or laterPost 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.
This page as .md · .json · 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.