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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.8.203
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. GeoDirectory WordPress plugin version 2.8.202 or earlier
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 19/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Read the original 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.
Who should check
Sites and teams running the WordPress GeoDirectory plugin version 2.8.202 or earlier
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
GeoDirectory WordPress plugin version 2.8.202 or earlierUpgrade to a fixed version: 2.8.203.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- geodirectory
through 2.8.202
Evidence 2
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124250
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: cve.now feed data
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: patchstack.com, cve.org
Which versions are affected by CVE-2026-124250?
geodirectory: through 2.8.202.Source: cve.now feed data
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: patchstack.com, cve.org
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: patchstack.com, cve.org