Skip to main content

GeoDirectory EUVDEUVD-2026-102831

| CVE-2026-110703 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-10-16 Wordfence GHSA-x86j-gh72-fxvv
6.4
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Register subscriber and obtain published listing
  2. Delivery
    Edit post_content with XSS payload via ajax_save_post
  3. Exploit
    Published status re-applied, bypassing re-moderation
  4. Execution
    Script stored and served live on listing page
  5. Impact
    Victim views page, script executes in browser

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated account with subscriber-level access or above (PR:L) AND the attacker must OWN an already-published listing, because the GeoDir_Post_Data::can_edit() ownership check restricts who can store the payload - a new or pending submission would normally face moderation. The specific abusable condition is that ajax_save_post() re-applies the existing post_status on edit, so modifying an already-published listing bypasses re-moderation and the injected 'post_content' script is served immediately. Limiting factors: requires valid authentication and prior listing ownership/publication, so sites that disable open registration, do not allow front-end listing submission, or hold all listings in moderation are substantially less exposed. The payload executes passively when any user views the injected listing page.

Impact

This is a moderate-severity stored XSS (CVSS 6.4, CWE-79) reported by Wordfence against the GeoDirectory WordPress plugin. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N indicates network-reachable, low-complexity exploitation by an authenticated low-privileged (PR:L, subscriber-level) attacker with a changed scope and low confidentiality/integrity impact. No EPSS score, KEV listing, or public POC was provided; this vulnerability is NOT in CISA KEV and there is no public exploit identified at time of analysis, so there is no evidence of active exploitation. The practical risk is tempered by meaningful preconditions the raw CVSS does not fully capture: the attacker must already own a PUBLISHED listing because GeoDir_Post_Data::can_edit() enforces an ownership check, so this is not a spray-and-pray flaw. The genuinely notable element is a moderation-bypass: ajax_save_post() re-applies the existing post_status, so edits to an already-published listing skip re-moderation and the payload goes live immediately - this is what elevates it from theoretical to realistically abusable on sites that accept user-submitted listings. Signals are internally consistent (low-privilege authenticated stored XSS) with no conflicts; treat as a genuine but non-emergency patch priority, prioritized higher for directory sites with open subscriber registration and publicly viewable listings.

Exploit ScenarioDerived

An attacker registers as a subscriber on a GeoDirectory-powered site and gets a listing published (or already owns one). They then edit the listing's 'post_content' with a malicious script payload; because ajax_save_post() preserves the published status, the edit bypasses re-moderation and goes live instantly. Any visitor or administrator who views the listing page executes the attacker's JavaScript in their browser session. No public POC was provided in the input data.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 16, 2026

Stored cross-site scripting in the GeoDirectory - WP Business Directory Plugin and Classified Listings Directory for WordPress (all versions up to and including 2.8.191) allows authenticated attackers with subscriber-level access or above to inject arbitrary JavaScript into a listing's post_content that then executes in the browser of any visitor viewing that listing page. The attacker must own an already-published listing, because the GeoDir_Post_Data::can_edit() ownership check limits who can store the payload and ajax_save_post() re-applies the existing post_status on edit, so changes to a published listing bypass re-moderation and go live immediately; sites that disable open registration, disallow front-end submissions, or hold listings in moderation are substantially less exposed. This moderate-severity flaw (CVSS 6.4, CWE-79) was reported by Wordfence, and no public exploit identified at time of analysis (it is not listed in CISA KEV).

RemediationAI

An upstream fix is available as a plugin Trac changeset (revision 3746728: https://plugins.trac.wordpress.org/changeset?reponame=&old=3746728%40geodirectory&new=3746728%40geodirectory), but a released patched version number is not independently confirmed from the provided data; update GeoDirectory to the latest available release beyond 2.8.191 and confirm the changelog references this issue. Because the attack requires an authenticated account that already owns a published listing, the most effective compensating control is to restrict who can own and publish listings - for example, disable open registration and front-end listing submission for subscriber-level roles, or require an elevated capability (editor/administrator) for listing edits. The trade-off is significant: disabling front-end submission breaks the plugin's core directory workflow, and moderation alone is insufficient because ajax_save_post() re-applies the existing post_status, bypassing re-moderation of edits to already-published listings. Supporting measures include scanning existing published listings for injected script tags in post_content and applying a WAF rule that blocks or sanitizes script markup in listing submission requests, though such rules may cause false positives on legitimate embeds. Consult the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/2af46137-6cdc-4898-8d59-3c603ebe02c4?source=cve) for updated patch guidance.

Affected VersionsENISA

GeoDirectory – WP Business Directory Plugin and Classified Listings Directory 0 ≤2.8.191

Affected Packages

euvd geodirectory_wp_business_directory_plugin_and_classified_listings_directory no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The issue is a stored (persistent) cross-site scripting vulnerability (CWE-79) in a WordPress plugin that handles user-submitted business directory listings. GeoDirectory saves listing content into the WordPress post_content field, and the plugin fails to sanitize that input on save and to escape it on output, so script markup persists in the database and is rendered into the page body for every subsequent visitor. The affected code paths cited in the advisory are the AJAX save handler in includes/class-geodir-ajax.php (ajax_save_post(), around line 821), the ownership check in includes/class-geodir-post-data.php (GeoDir_Post_Data::can_edit(), around line 1661), and related post handling in includes/post-functions.php (around line 2032); a reference to the bundled AyeCode UI library (vendor/ayecode/wp-ayecode-ui/includes/inc/bs5-js.php, around line 328) points to the rendering sink. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N describes a network-reachable, low-complexity attack requiring low privileges and no user interaction, with scope change because the injected script runs in the context of the site's own pages, and limited confidentiality and integrity impact; availability is unaffected. The CPE string cpe:2.3:a:paoltaia:geodirectory_-_wp_business_directory_plugin_and_classified_listings_directory:*:*:*:*:*:*:*:* uses a wildcard version, reflecting that the identifier treats the paoltaia/GeoDirectory plugin as affected without naming a fixed release.

Know when Wordpress Plugin gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Wordfence) PRIMARY 6.4 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
vuln.today AI 6.4 MEDIUM

Authenticated subscriber (PR:L) injects stored script over the network (AV:N); scope changes into victim browsers (S:C) with low C/I impact and no availability effect; UI:N as payload executes on normal page view.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

DescriptionCVE.org

The GeoDirectory - WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_content' parameter in all versions up to, and including, 2.8.191 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the attacker to own a published listing, as the ownership check in GeoDir_Post_Data::can_edit() limits who can store the payload; however, because ajax_save_post() re-applies the existing post_status, edits to an already-published listing bypass re-moderation and remain live immediately.

Threat Intelligence Overview

EPSS Score
0.4%
Top 70% exploitable
Prevalence
Medium
popular WordPress directory plugin, common but not on most sites
Social Media
1
Sightings
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

CVE-2024-5084 CRITICAL POC
9.8 May 23

The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil

CVE-2024-44000 CRITICAL POC
9.8 Oct 20

Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote

CVE-2020-36847 CRITICAL POC
9.8 Jul 12

The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner

CVE-2025-27007 CRITICAL POC
9.8 May 01

The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut

CVE-2016-1209 CRITICAL POC
9.8 May 14

The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via

CVE-2024-4443 CRITICAL POC
9.8 May 22

The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based

CVE-2024-1698 CRITICAL POC
9.8 Feb 27

SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a

CVE-2023-6875 CRITICAL POC
9.8 Jan 11

The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i

CVE-2024-1512 CRITICAL POC
9.8 Feb 17

The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base

CVE-2024-4295 CRITICAL POC
9.8 Jun 05

The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in

CVE-2024-50498 CRITICAL POC
10.0 Oct 28

Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy