Quick answers
- Is CVE-2026-120082 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120082 being exploited in the wild.
- How severe is CVE-2026-120082?
- High severity, with a CVSS score of 7.2, published 7 November 2026.
- Which products and versions are affected?
- AyeCode GeoDirectory up to and including 2.8.200.
- Is there a fix for CVE-2026-120082?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-120082 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-120082?
- Check whether you run AyeCode 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.
Technical details
A stored cross-site scripting vulnerability exists in GeoDirectory through version 2.8.200 due to insufficient input sanitization and output escaping in the post_content parameter. The vulnerability exploits WordPress's single-pass shortcode stripping mechanism; attackers can nest shortcodes (e.g., [gd_dynamic_content[gd_tags]t]) to bypass the geodir_strip_shortcodes() filter, and HTML-entity-encoded shortcode attributes survive wp_kses_post() filtering since it inspects HTML tags rather than shortcode attribute values. Unauthenticated attackers can inject arbitrary scripts that persist in the database and execute for all page visitors.
Affected products
- AyeCode GeoDirectory up to and including 2.8.200
Timeline
- 2026-11-07: disclosed