# CVE-2026-113491: GeoDirectory WordPress plugin path traversal in file handling

Source: https://junglewise.ai/threats/cve-2026-113491-the-geodirectory-wordpress-plugin-before-2-8-194-does-not  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-24. Updated: 2026-10-24  
License: CC BY 4.0 with a link back

CVE-2026-113491 · Severity: info · Published 2026-10-24

GeoDirectory is a WordPress plugin used to create location-based directory listings. The plugin fails to validate user-supplied image URLs before using them as file paths when saving front-end listings, allowing attackers with basic user access to read sensitive files from outside the web root and delete files on the server. Disclosed files are exposed at public URLs and then deleted, enabling information theft and denial of service.

Technologies: [GeoDirectory](https://junglewise.ai/threats/technologies/geodirectory-geodirectory). Vendors: [GeoDirectory](https://junglewise.ai/threats/vendors/geodirectory).

## Quick answers

**Is CVE-2026-113491 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-113491 being exploited in the wild.

**How severe is CVE-2026-113491?** Informational severity, published 24 October 2026.

**Which products and versions are affected?** GeoDirectory before 2.8.194.

**Is there a fix for CVE-2026-113491?** Yes: fixed in 2.8.194. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-113491 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-113491?** 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.194

## Technical details

The vulnerability is a path traversal flaw (CWE-22) where user input for image URLs is not validated before being interpreted as local file paths. Attackers with Subscriber-level access or above can exploit this to access files outside the intended directory and perform arbitrary file deletion, though exploitation is limited to files with allowed media extensions. The flaw affects versions before 2.8.194 and permits both local file read and deletion operations.

## Affected products

- GeoDirectory GeoDirectory before 2.8.194

## Timeline

- 2026-10-22: disclosed
- 2026-10-24: patched

## References

- [https://wpscan.com/vulnerability/ba2114a5-01e3-40e7-a7f6-673674b6501d/](https://wpscan.com/vulnerability/ba2114a5-01e3-40e7-a7f6-673674b6501d/)

## Related threats

- [GeoDirectory WordPress plugin password-protected listing disclosure](https://junglewise.ai/threats/cve-2026-114270-the-geodirectory-wordpress-plugin-before-2-8-197-does-not-honour)
- [GeoDirectory WordPress plugin information disclosure via shortcode](https://junglewise.ai/threats/cve-2026-113494-the-geodirectory-wordpress-plugin-before-2-8-195-does-not)
- [GeoDirectory WordPress plugin stored XSS in post badge shortcode](https://junglewise.ai/threats/cve-2026-113488-the-geodirectory-wordpress-plugin-before-2-8-196-does-not)
- [GeoDirectory WordPress plugin stored XSS in post badge link](https://junglewise.ai/threats/cve-2026-113487-the-geodirectory-wordpress-plugin-before-2-8-196-does-not)
- [GeoDirectory WordPress plugin authorization bypass in guest listing](https://junglewise.ai/threats/cve-2026-113674-the-geodirectory-wordpress-plugin-before-2-8-194-does-not)