Skip to main content

GeoDirectory EUVDEUVD-2026-111725

| CVE-2026-113487 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-10-28 contact@wpscan.com GHSA-64wh-p786-vprv
6.8
CVSS 3.1 · Vendor: wpscan
View

Attack ChainAIDerived

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

  1. Access
    Obtain Contributor account on target site
  2. Delivery
    Inject payload into post badge click-through link
  3. Exploit
    Store malicious listing awaiting moderation
  4. Execution
    Admin views listing to moderate
  5. Persist
    Script executes in admin session
  6. Impact
    Hijack admin session / perform admin actions

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

Requires an authenticated account with the Contributor role or higher on the target WordPress site - so exploitation is limited to deployments that provision such accounts to untrusted or semi-trusted users (community submissions, multi-author directories). The attacker must set the post badge click-through link value on a listing, and the payload only fires when a higher-privileged user (the description names an administrator reviewing moderated content) actually views the affected listing, i.e. user interaction by the victim is required (UI:R). Sites that do not grant Contributor-level access to untrusted parties, or that do not have admins manually review listings, are materially less exposed. The complete fix is updating to GeoDirectory 2.8.196; no vendor-provided mitigation other than updating is stated in the available sources.

Impact

This is a moderate, authenticated stored XSS in the GeoDirectory WordPress plugin, and the signals are internally consistent in pointing to a non-emergency but patch-worthy issue. Exploitation status is 'no public exploit identified at time of analysis' - the only references are the WPScan advisory and the NVD entry, neither of which is working exploit code, and the vulnerability is NOT in CISA KEV. EPSS is low (0.17%, 6th percentile), consistent with the absence of public exploitation and with the fact that the attack requires an authenticated foothold plus victim interaction. The supplied CVSS vector (AV:N/AC:L/PR:H/UI:R/S:U, 6.8) and the description are partly in tension: the description says a Contributor-role user (a low-privilege authenticated account) can inject the payload, which argues for PR:L rather than the PR:H shown in the vector - verify privilege level with the advisory. The vector also marks Scope Unchanged (S:U), but because the injected script executes in the browser/session of a higher-privileged victim (an administrator moderating content), a scope-change (S:C) reading is defensible. The vuln.today decision label is 'this_month', which aligns with the low EPSS and absence of KEV/PoC: schedule the update in a normal patch cycle rather than treating it as an emergency. Net: a real priority for sites that allow untrusted Contributor accounts, but not a mass-exploitation threat.

Exploit ScenarioDerived

A site operator grants Contributor accounts (e.g. to community members submitting business listings). A malicious Contributor creates or edits a listing and sets a post-badge click-through link value containing a crafted payload that is not sanitised/escaped when rendered inside an anchor element. When an administrator later opens that listing to moderate the pending content, the stored script executes in the administrator's authenticated session. No public exploit code is identified at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 28, 2026

Stored cross-site scripting in the GeoDirectory WordPress plugin before 2.8.196 allows authenticated users holding the Contributor role or higher to save a malicious post badge click-through link value on a listing, which is later rendered without proper sanitisation or escaping in an anchor element. The payload executes in the browser of any higher-privileged user who views the affected listing - the advisory specifically calls out an administrator reviewing moderated content - but only after that victim opens the listing, so user interaction is required. Exposure is concentrated on community and multi-author directory sites that hand Contributor-level accounts to semi-trusted users and have admins manually review submissions; EPSS is 0.17% (6th percentile), there is no KEV listing, and no public exploit is identified at time of analysis, which supports a patch-worthy but non-emergency priority of fixing this month. The complete fix is updating to GeoDirectory 2.8.196.

RemediationAI

Update the GeoDirectory plugin to version 2.8.196, which the vendor makes available as the complete fix; the available sources state no vendor-provided mitigation other than updating, so no official workaround or configuration toggle is documented. Confirm the update through the WordPress plugin administration screen or by deploying the 2.8.196 release, and verify the installed version afterwards, referencing the WPScan advisory at https://wpscan.com/vulnerability/0117ed44-672d-4308-9fa0-0eb04fccd255/ for details. Until the update is applied, exposure can be reduced by not provisioning Contributor-or-above accounts to untrusted or semi-trusted users on directory sites and by reviewing which accounts can edit listing badge link values, since exploitation requires such an account to plant the stored payload and an administrator to then view the affected listing - but these are exposure-reduction considerations rather than vendor-endorsed mitigations, and they do not remove the underlying output-encoding defect. Given a 'this_month' priority, an EPSS of 0.17% and no KEV listing, scheduling the upgrade in the current patch cycle is appropriate.

Affected VersionsENISA

GeoDirectory 0 <2.8.196

Affected Packages

euvd geodirectory fix: 2.8.196

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

GeoDirectory is a WordPress directory/listing plugin in which listings are custom post types that carry badges with click-through link values; the flaw is CWE-79 (improper neutralisation of input during web page generation), specifically a stored/persistent XSS where the badge link value is saved from a privileged-but-low-trust editing context and then written into an anchor element without output encoding. Because the value lands in markup rather than being escaped for the HTML attribute context, an attacker-supplied string can break out and inject script that persists in the database and fires for every subsequent viewer of the listing. The independent assessment scores this CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N, i.e. network-reachable, low attack complexity, requiring an authenticated Contributor-or-above account, with victim interaction and a scope change reflecting execution in the higher-privileged victim's session; note the vendor/CVSS 6.8 vector in the source data instead rates privileges required as high, while the assessment places the prerequisite at Contributor level. Successful exploitation runs script in an administrator's authenticated context, so confidentiality and integrity impact are high while availability impact is none. The trigger path beyond 'set the badge click-through link value, then have a higher-privileged user view the listing' is not further described in the available sources.

Know when WordPress 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 (wpscan) PRIMARY 6.8 MEDIUM
AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 8.7 HIGH

Contributor is a low-privilege authenticated account (PR:L, not PR:H); victim admin must view the listing (UI:R); script runs in the admin's context so scope changes (S:C); session/content takeover gives C:H/I:H, no direct availability loss (A:N).

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

Primary rating from Vendor (wpscan).

CVSS VectorVendor: wpscan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Oct 28, 2026 - 18:22 NVD
6.8 (MEDIUM)
Patch available
Oct 28, 2026 - 07:16 EUVD
CVE Published
Oct 28, 2026 - 06:16 cve.org
MEDIUM 6.8
CVE Published
Oct 28, 2026 - 06:16 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

The GeoDirectory WordPress plugin before 2.8.196 does not properly sanitise or escape a post badge click-through link value before outputting it in an anchor element on a listing, allowing users with the Contributor role and above to perform Stored Cross-Site Scripting attacks against higher-privileged users who view the listing, including an administrator reviewing moderated content.

Threat Intelligence Overview

EPSS Score
0.2%
Top 94% exploitable
Prevalence
Medium
popular WordPress directory/listings plugin, tens of thousands of installs
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.2%
Patch available Yes
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· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
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-2016-10033 CRITICAL POC
9.8 Dec 30

The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para

CVE-2016-10045 CRITICAL POC
9.8 Dec 30

The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman

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-2024-8353 CRITICAL POC
9.8 Sep 28

The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all

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-11749 CRITICAL POC
9.8 Nov 05

The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint

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-2026-63030 CRITICAL POC
9.8 Jul 17

Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r

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