Quick answers
- Is CVE-2026-114270 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114270 being exploited in the wild.
- How severe is CVE-2026-114270?
- Informational severity, published 29 October 2026.
- Which products and versions are affected?
- GeoDirectory before 2.8.197.
- Is there a fix for CVE-2026-114270?
- Yes: fixed in 2.8.197. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-114270 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-114270?
- 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.197
Technical details
The plugin does not honour post password protection when rendering listings, failing to validate password authentication before displaying protected content. An unauthenticated attacker can directly access the listing output and extract both the main content and custom field data without any authentication. The vulnerability is fixed in version 2.8.197.
Affected products
- GeoDirectory GeoDirectory before 2.8.197
Timeline
- 2026-10-27: disclosed
- 2026-10-29: advisory