Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-105078 Overview
CVE-2026-105078 is a stored cross-site scripting (XSS) vulnerability in the WP Store Locator WordPress plugin. The flaw affects all versions up to and including 3.0.3. An authenticated attacker with low privileges can inject malicious scripts that persist in the application and execute in the browsers of other users who view the affected content.
The vulnerability is classified under CWE-79, Improper Neutralization of Input During Web Page Generation. Exploitation requires user interaction and crosses a security scope boundary, allowing attackers to impact confidentiality, integrity, and availability of victim sessions.
Critical Impact
Authenticated attackers can inject persistent JavaScript that executes against site visitors and administrators, enabling session theft, administrative action hijacking, and content manipulation on WordPress sites running vulnerable WP Store Locator installations.
Affected Products
- WP Store Locator plugin for WordPress — versions up to and including 3.0.3
- WordPress sites with the wp-store-locator plugin installed and enabled
- Any site administrator or visitor rendering plugin-generated store locator content
Discovery Timeline
- 2026-10-08 - CVE-2026-105078 published to the National Vulnerability Database
- 2026-10-08 - Last updated in NVD database
Technical Details for CVE-2026-105078
Vulnerability Analysis
The WP Store Locator plugin fails to properly neutralize user-supplied input before rendering it in generated web pages. An authenticated user with sufficient privileges to submit or modify store locator content can embed JavaScript payloads that the plugin stores server-side.
When another user, including administrators, loads a page that renders this stored content, the browser executes the attacker's script in the context of the WordPress site origin. Stored XSS is more severe than reflected variants because the payload persists and executes automatically for every subsequent visitor to the affected view.
The scope change recorded in the CVSS vector indicates the vulnerable component can affect resources beyond its own security authority. In practice, a payload injected through the plugin can act against the broader WordPress session and dashboard.
Root Cause
The root cause is missing or insufficient output encoding of user-controlled fields handled by the plugin before they are rendered as HTML. Input intended to describe stores, locations, or related metadata is written back into the page without escaping characters such as <, >, and quotation marks.
Attack Vector
Exploitation requires network access to the WordPress site and low-privilege authenticated access to the plugin's input fields. The attacker submits crafted content containing an XSS payload through the plugin's data entry workflow.
Triggering the payload requires a victim to view the rendered page containing the stored input. When an administrator views the affected content, the attacker can perform actions in that administrator's context, including creating accounts, modifying plugin settings, or exfiltrating session cookies.
No verified public exploit code or proof-of-concept has been published at the time of this writing. Refer to the Patchstack XSS Vulnerability Advisory for additional technical context.
Detection Methods for CVE-2026-105078
Indicators of Compromise
- Unexpected <script> tags, javascript: URIs, or HTML event handlers (onerror, onload, onmouseover) stored in wp_wpsl_stores or related plugin tables
- WordPress administrator accounts created or elevated shortly after an admin viewed store locator pages
- Outbound HTTP requests from administrator browsers to attacker-controlled hosts after loading plugin content
- Modifications to plugin settings or theme files that correlate with administrator sessions viewing locator data
Detection Strategies
- Query the WordPress database for plugin-managed fields containing HTML tags, script content, or encoded JavaScript keywords
- Monitor web server access logs for POST requests to plugin AJAX endpoints submitting payloads with angle brackets or script keywords
- Deploy a web application firewall rule set that inspects submissions to wp-admin/admin-ajax.php and plugin REST routes for XSS signatures
Monitoring Recommendations
- Enable WordPress audit logging for plugin configuration changes, user creation, and role modifications
- Alert on administrator account activity immediately following page views of store locator content
- Track browser Content Security Policy (CSP) violation reports originating from pages rendered by wp-store-locator
How to Mitigate CVE-2026-105078
Immediate Actions Required
- Audit WP Store Locator records for existing malicious content and remove any entries containing script tags or JavaScript handlers
- Restrict plugin edit privileges to trusted accounts and review which roles can submit or modify store entries
- Rotate credentials and session tokens for any administrator who viewed plugin content while the site ran version 3.0.3 or earlier
Patch Information
At the time of publication, the vendor advisory tracked by Patchstack lists versions through 3.0.3 as affected. Review the Patchstack XSS Vulnerability Advisory for the latest fixed version and apply the update through the WordPress plugin manager once available.
Workarounds
- Disable and remove the WP Store Locator plugin until a patched version is installed if store locator functionality is non-essential
- Deploy a Content Security Policy that disallows inline scripts and restricts script sources to trusted origins
- Place a web application firewall in front of WordPress with rules that block XSS payloads targeting the plugin's input parameters
- Limit contributor and editor accounts to the minimum required, and enforce multi-factor authentication for all administrative users
# Example Content Security Policy header to limit XSS impact
Header set Content-Security-Policy "default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

