CVE-2026-113487VulnerabilityPublished 28 Oct 2026

The GeoDirectory WordPress plugin before 2.8.196 does not properly sanitise or escape a post badge click-through link

Source GCVE Database

Authoritative record:CVE-2026-113487· High

Not known to be exploited : upgrade to 2.8.196 soon.

Data as of 28 Oct 2026, 07:14 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch: Available – fixed in 2.8.196

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-64wh-p786-vprv

What to do

Upgrade GeoDirectory (WordPress plugin) to 2.8.196.

Affected software

Product	Affected	Fixed in
GeoDirectory	Affected <2.8.196	Fixed in 2.8.196

AI-suggested

A fix is available in GeoDirectory plugin version 2.8.196. Users should upgrade to version 2.8.196 or later to remediate this vulnerability. No additional mitigation steps are indicated in the provided data.

Description

The GeoDirectory WordPress plugin versions before 2.8.196 contain a vulnerability where a post badge click-through link is not properly sanitized or escaped. This flaw allows users with Contributor role or higher to inject stored cross-site scripting (XSS) payloads that execute when higher-privileged users, such as administrators, view the affected listing.

Impact

Stored cross-site scripting allows an attacker with Contributor-level access to inject malicious scripts that execute in the browsers of higher-privileged users viewing the listing. This can lead to unauthorized actions performed with the privileges of the victim user, including administrators, potentially compromising site integrity and security.

Summary

The GeoDirectory WordPress plugin prior to version 2.8.196 fails to properly sanitize or escape the value of a post badge click-through link before outputting it in an anchor element on listings. This improper handling enables users with the Contributor role and above to perform stored cross-site scripting attacks. The malicious script is stored in the listing and executed in the context of higher-privileged users, including administrators reviewing moderated content, potentially leading to session hijacking or other XSS-related impacts.

References

Community reviews

Loading reviews…