CVE-2026-0563
BaseFortify
Publication date: 2026-01-09
Last updated on: 2026-01-09
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordfence | wp_google_street_view | to 1.1.8 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Stored Cross-Site Scripting (XSS) issue in the WP Google Street View & Google maps + Local SEO WordPress plugin. It occurs via the 'wpgsv_map' shortcode in versions up to 1.1.8 due to insufficient input sanitization and output escaping. Authenticated users with contributor level access or higher can inject malicious scripts into pages, which then execute whenever those pages are viewed by users. [1]
How can this vulnerability impact me? :
The vulnerability allows attackers with contributor or higher access to inject arbitrary scripts into pages. This can lead to malicious code execution in users' browsers when they visit the affected pages, potentially resulting in theft of user data, session hijacking, or other malicious actions that compromise site security and user trust. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by scanning your WordPress installation for the presence of the vulnerable WP Google Street View plugin version 1.1.8 or earlier. Additionally, look for usage of the 'wpgsv_map' shortcode in posts or pages that might contain injected scripts. Since the vulnerability involves stored cross-site scripting via shortcode attributes, inspecting database entries for suspicious scripts in the 'wpgsv_map' shortcode parameters can help. Specific commands are not provided in the resources. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the WP Google Street View plugin to a version that includes the security fix, which improves input sanitization and output escaping in the 'includes/shortcode.php' file. This update applies functions like wp_kses_post() and esc_attr() to sanitize user inputs and shortcode attributes, preventing stored cross-site scripting attacks. Until the update is applied, restrict contributor-level access to trusted users only to reduce risk. [1]