Quick answers
- Is CVE-2026-113487 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113487 being exploited in the wild.
- How severe is CVE-2026-113487?
- Informational severity, published 28 October 2026.
- Which products and versions are affected?
- GeoDirectory before 2.8.196.
- Is there a fix for CVE-2026-113487?
- Yes: fixed in 2.8.196. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-113487 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-113487?
- 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.196
Technical details
The gd_post_badge shortcode does not sanitize or escape the 'link' attribute before outputting it in an anchor element's href, allowing authenticated users with Contributor role or above to inject JavaScript. The vulnerability is a stored XSS requiring authentication but affecting higher-privileged users who view affected listings, including administrators reviewing moderated content. The issue was fixed in version 2.8.196.
Affected products
- GeoDirectory GeoDirectory before 2.8.196
Timeline
- 2026-10-26: disclosed