GEO my WP ≤ 4.5.5.3: Unauthenticated PHP Object Injection in the Location Plugin (CVE-2026-61992, CVSS 9.8)

Running GEO my WP on your site? Check it against CVE-2026-61992 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your GEO my WP is in the affected range (≤ 4.5.5.3), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

GEO my WP ≤ 4.5.5.3: Unauthenticated PHP Object Injection in the Location Plugin (CVE-2026-61992, CVSS 9.8)

The plugin that plots your locations on a map — the store finder, the member directory, the dealer locator — accepted untrusted serialized data from visitors with no account at all. CVE-2026-61992 is an unauthenticated PHP object injection flaw in GEO my WP (the "GEO my WordPress" plugin), and it carries a CVSS score of 9.8.

What Happened

CVE-2026-61992 is a PHP object injection vulnerability (CWE-502, deserialization of untrusted data) in the GEO my WP WordPress plugin, disclosed October 29, 2026 (CNA: Patchstack). The plugin sits on 3,000+ sites.

What Object Injection Means, Honestly

Object injection is not automatic code execution. An attacker supplies a crafted serialized object; what happens next depends on whether some other plugin or theme on the same site provides a usable gadget chain that turns that object into file deletion, option changes, or code execution. A minimal site might have no chain. A directory or listing site — map tools, membership plugins, form builders, payment add-ons — carries many candidate chains. That uncertainty is not reassurance: it is the reason a 9.8 object-injection flaw gets patched the day you hear about it, not the week after.

Am I Affected?

Check wp-admin → Plugins for GEO my WP and its version. At 4.5.5.3 or below, you are in the affected range.

This one is version-checkable, and our scanner checks it: the free mini-scan reads the plugin's public readme and flags a stable tag at or below 4.5.5.3 as a High finding naming CVE-2026-61992. It reads the version only — it never sends a serialized payload, and it never exercises the flaw. A version above the affected range earns no "patched" claim from us, because the CVE record's own fix fields conflict — that silence is deliberate, and it is the honest reading of the primary source.

What To Do Now

  1. Update GEO my WP to the latest available version today — the current release (4.5.5.7 at writing), not merely the first version past the affected range.
  2. Review administrator accounts and uploaded files. Object injection is a code-execution-class flaw when a gadget chain is present; anything you don't recognize deserves a closer look.
  3. Put location and directory plugins on payment-plugin discipline. They parse stranger input all day — addresses, coordinates, search terms — and they belong on the same update schedule as the plugins that take cards.

The Bigger Lesson

When an AI builder assembles a directory or listing site, it installs the interactive stack fast: maps, locations, forms, memberships. Each of those plugins becomes part of the site's attack surface with exactly the access it needs to move data around. The pre-ship question is not "does the map work?" — it's "what version is it on, and who updates it when a 9.8 lands?" Nobody asking that question is being slow. They're being done.

Related: WordPress Hardening for AI-Built Sites — the standing version of this discipline. How to Check If Your Web App Is Hacked — the follow-up pass if the review step finds a stranger's work.


Running GEO my WP? Update to the latest release, then run the free check at preshipit.com/free-scan — it flags GEO my WP ≤ 4.5.5.3 and the rest of your site's exposed surface in about a minute.

Check GEO my WP on your own site — free.

Our free WordPress Plugin Vulnerability Checker pulls GEO my WP's current version from wordpress.org and lists the vulnerabilities our scanner checks for — CVE-2026-61992 included. No scan, no account.

Open the free plugin checker →

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Running GEO my WP on your site? Check it against CVE-2026-61992 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your GEO my WP is in the affected range (≤ 4.5.5.3), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report