Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconObtain WordPress admin credentials via phishing or reuse
-
DeliveryAccess Store Locator plugin settings page
-
ExploitInject XSS payload into vulnerable unsanitized setting
-
InstallSave malicious payload to database
-
C2Wait for super admin to visit affected admin page
-
ExecuteStored script executes in super admin's browser
-
ImpactExfiltrate session cookie or perform privileged network-wide 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 | Exploitation requires the attacker to already possess WordPress administrator-level credentials for the target site (confirmed by CVSS PR:H). The Store Locator WordPress plugin must be installed, active, and running a version prior to 1.6.6. A second privileged user (administrator or super admin) must visit the admin page where the malicious payload is rendered (CVSS UI:R). The vulnerability is especially impactful in WordPress multisite networks where the |
| Impact | The CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N) scores 3.5 (Low), reflecting two significant exploitation constraints: high privilege required (PR:H - administrator-level access to the plugin settings) and required user interaction (UI:R - a second privileged user must visit the admin page). Scope is unchanged (S:U), and impact is limited to low confidentiality and integrity effects in isolation. No EPSS score was provided, so probabilistic exploitation likelihood cannot be quantified from this dataset. The CVE is not listed in the CISA KEV catalog, indicating no confirmed mass exploitation at time of analysis. However, a publicly available exploit via WPScan lowers the attacker skill threshold considerably. The raw CVSS score underweights the multisite privilege-escalation vector: an attacker with subsite-admin credentials - a relatively common role in large WordPress networks - can target super admins who visit the page, effectively achieving upward privilege impact not reflected in the S:U scope designation. For single-site installs, risk aligns with the low CVSS score. For multisite networks, this should be treated as moderate priority. |
| Exploit ScenarioDerived | An attacker with WordPress administrator credentials navigates to the Store Locator plugin's settings page and saves a malicious JavaScript payload (e.g., a cookie-stealing script) into the vulnerable, unescaped settings field. When a super admin or other privileged user subsequently visits the admin page where the setting is rendered, the stored payload executes silently in their browser session. In a multisite environment, this allows a subsite admin to harvest the super admin's session token, enabling full network takeover. A publicly available exploit via WPScan means this attack pattern is accessible to low-skill adversaries who have already obtained admin credentials through phishing or credential stuffing. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 10, 2026
Stored Cross-Site Scripting in Store Locator WordPress plugin before 1.6.6 allows administrator-level users to inject persistent malicious scripts into the plugin's admin settings page, with execution triggered when any privileged user visits the page. Critically, this bypass works even when WordPress's unfiltered_html capability is restricted - a control commonly enforced in multisite networks - meaning a subsite admin could target visiting super admins. A publicly available exploit exists via WPScan, though no active exploitation has been confirmed by CISA KEV. CVSS rates this 3.5 (Low), but multisite deployments face materially higher practical risk.
RemediationAI
Update the Store Locator WordPress plugin to version 1.6.6 or later, which contains the vendor-released patch resolving the unsanitized settings input. The fix is confirmed available per the WPScan advisory at https://wpscan.com/vulnerability/1ed01413-09a2-4a2e-be5b-375f2a327d0d/. In WordPress admin, navigate to Plugins > Installed Plugins > Store Locator > Update to apply. If immediate patching is blocked, the most effective compensating control in multisite deployments is to audit and minimize which users hold site-admin roles on subsites, reducing the pool of potential attackers. Restricting access to the Store Locator settings page via role-based access control plugins (e.g., restricting the relevant admin menu capability) may limit exposure but requires plugin-specific configuration and should not be treated as a permanent fix. Relying solely on disabling unfiltered_html is explicitly insufficient - this vulnerability bypasses that control by design.
Affected VersionsENISA
Affected Packages
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 vulnerability is a Stored XSS flaw (CWE-79: Improper Neutralization of Input During Web Page Generation) in the Store Locator WordPress plugin (CPE: cpe:2.3:a:unknown:store_locator_wordpress:*:*:*:*:*:*:*:*, all versions before 1.6.6). The root cause is the plugin's failure to sanitize and escape a settings field before persisting it to the database and rendering it back on the admin page - the standard sink/source XSS pattern. What elevates this beyond a typical admin-context XSS is that the flaw operates independently of WordPress's built-in unfiltered_html capability gate, a permission flag multisite networks routinely restrict to limit HTML injection by non-super-admin administrators. The plugin does not route this input through WordPress's escaping pipeline (e.g., esc_attr() or esc_html() on output, or sanitize_text_field() on save), making the native WordPress access control an ineffective compensating control here.
Know when Store Locator 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
AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N
Primary rating from Vendor (WPScan) · only source for this CVE.
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The Store Locator WordPress plugin before 1.6.6 does not sanitize and escape one of its settings before storing it and outputting it on the Store Locator WordPress plugin before 1.6.6 admin page, allowing high-privileged users such as administrators to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (e.g. in a multisite network where the super admin visits the page).
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Store Locator Wordpress
View allStored XSS in the Store Locator WordPress plugin before 1.6.9 allows high-privileged users (administrators) to inject pe
Path traversal in the Store Locator WordPress plugin before version 1.6.9 enables authenticated administrators to read a
EUVD-2026-35987
GHSA-q278-422p-x5h7
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB