---
id: "CVE-2026-116752"
kind: "vulnerability"
aliases: ["CVE-2026-116752"]
title: "GeoDirectory WordPress plugin: stored XSS via post_images lets subscribers run scripts"
severity: "medium"
cvss: 6.4
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["geodirectory", "package", "self-hosted", "wordpress"]
not_affected_if: ["patched-version", "plugin-not-installed"]
published_at: "2026-10-31T10:16:37+00:00"
first_seen_at: "2026-10-31T10:34:56+00:00"
updated_at: "2026-10-31T10:35:58+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-116752", "first_seen_at": "2026-10-31T10:34:56+00:00"}]
---

# GeoDirectory WordPress plugin: stored XSS via post_images lets subscribers run scripts

The GeoDirectory WordPress plugin, all versions up to and including 2.8.197, does not sanitize the 'post_images' parameter, enabling stored cross-site scripting. An authenticated subscriber can plant a script that runs in the browser of an administrator or editor who opens the pending listing's edit screen.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed GeoDirectory plugin version in the WordPress admin Plugins screen or `wp plugin get geodirectory --field=version`
- Treat sites running `2.8.197` or earlier as exposed

## Fix

- Move the GeoDirectory plugin to a version later than `2.8.197`; the sources do not name the fixed version

## Timeline

- 2026-10-31T10:34:56+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-116752

## From the sources

The GeoDirectory – WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_images' parameter in all versions up to, and including, 2.8.197 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The injected payload does not fire for the attacker directly; it executes in the browser of any Administrator or Editor who opens the pending listing's edit screen, making this a privilege-escalation-capable stored XSS chain triggered through normal editorial workflow.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_