Cross-Site Scripting (XSS) in Store Locator (WordPress plugin) (CVE-2026-9061)
Summary
Cross-site scripting in Store Locator (WordPress plugin) (CVE-2026-9061). Risk of unauthorized operations or information disclosure. Exploitable via unfiltered_html.
Original description
The description as published by the source.
The Store Locator WordPress plugin before 1.6.9 does not sanitize and escape store logo metadata before storing it and outputting it on the Store Locator WordPress plugin before 1.6.9 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).
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-9061 has been found in Store Locator (WordPress plugin).
Attackers can target a specific entry point like unfiltered_html over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Store Locator (WordPress plugin) CVE-2026-9061" on the vendor's site.
CVE-2026-9061 (Store Locator (WordPress plugin)) — CWE-79 / CVSS v3 3.5
Attack vector: remote (network-reachable)
Attack surface: unfiltered_html
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in Store Locator (WordPress plugin). Attackers reach the vulnerable code path via unfiltered_html.
Check the vendor advisory for the affected versions of Store Locator (WordPress plugin). Attack surface: unfiltered_html.
Severity: Low (CVSS 3.5/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Store Locator (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web contact@wpscan.com
- web nvd.nist.gov
- web wpscan.com
- web github.com