Quick answers
- Is CVE-2026-113494 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113494 being exploited in the wild.
- How severe is CVE-2026-113494?
- Informational severity, published 28 October 2026.
- Which products and versions are affected?
- GeoDirectory before 2.8.195.
- Is there a fix for CVE-2026-113494?
- Yes: fixed in 2.8.195. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-113494 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-113494?
- Check whether you run GeoDirectory at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.8.195
Technical details
The gd_post_content shortcode in GeoDirectory does not perform status or ownership validation when rendering listings referenced by an ID parameter, allowing authenticated users with Contributor role or above to retrieve non-public content belonging to other users. This is an information disclosure vulnerability (CWE-200) affecting the shortcode rendering logic with no special preconditions beyond having a Contributor account on the WordPress instance. A fix is available in version 2.8.195.
Affected products
- GeoDirectory GeoDirectory before 2.8.195
Timeline
- 2026-10-26: disclosed
- 2026-10-28: advisory