Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-0563: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in pagup WP Google Street View (with 360° virtual tour) & Google maps + Local SEO

0
Medium
VulnerabilityCVE-2026-0563cvecve-2026-0563cwe-79
Published: Fri Jan 09 2026 (01/09/2026, 06:34:53 UTC)
Source: CVE Database V5
Vendor/Project: pagup
Product: WP Google Street View (with 360° virtual tour) & Google maps + Local SEO

Description

CVE-2026-0563 is a stored Cross-Site Scripting (XSS) vulnerability in the WordPress plugin 'WP Google Street View (with 360° virtual tour) & Google maps + Local SEO' affecting all versions up to 1. 1. 8. Authenticated users with contributor-level access or higher can inject malicious scripts via the 'wpgsv_map' shortcode due to insufficient input sanitization and output escaping. These scripts execute whenever any user views the compromised page, potentially leading to session hijacking, data theft, or further attacks. The vulnerability has a CVSS score of 6. 4 (medium severity) and does not require user interaction but does require authenticated access with limited privileges. No known exploits are reported in the wild yet. European organizations using this plugin on WordPress sites are at risk, especially those with contributor-level user roles. Mitigation involves promptly updating the plugin once a patch is released or applying manual input validation and output escaping.

AI-Powered Analysis

AILast updated: 01/16/2026, 10:00:23 UTC

Technical Analysis

CVE-2026-0563 is a stored Cross-Site Scripting (XSS) vulnerability identified in the WordPress plugin 'WP Google Street View (with 360° virtual tour) & Google maps + Local SEO' developed by pagup. The vulnerability arises from improper neutralization of input during web page generation (CWE-79). Specifically, the 'wpgsv_map' shortcode does not adequately sanitize or escape user-supplied input before rendering it on pages. This flaw allows authenticated attackers with contributor-level permissions or higher to inject arbitrary JavaScript payloads into WordPress pages. When other users access these pages, the injected scripts execute in their browsers, potentially compromising session tokens, stealing cookies, or performing actions on behalf of the victim. The vulnerability affects all plugin versions up to and including 1.1.8. The CVSS 3.1 base score is 6.4, reflecting network attack vector (AV:N), low attack complexity (AC:L), requiring privileges (PR:L), no user interaction (UI:N), and impact on confidentiality and integrity (C:L, I:L) but not availability (A:N). The scope is changed (S:C) because the vulnerability affects resources beyond the attacker’s privileges. No public exploits are currently known, but the presence of stored XSS in a widely used WordPress plugin poses a significant risk, especially in environments with multiple contributors. The vulnerability can be exploited remotely over the network by authenticated users, making it a moderate but actionable threat.

Potential Impact

For European organizations, this vulnerability can lead to unauthorized script execution within trusted websites, resulting in session hijacking, credential theft, defacement, or malware distribution. Organizations relying on WordPress sites with multiple contributors, such as content teams or marketing departments, are particularly vulnerable since contributor-level access suffices for exploitation. The compromise of user sessions or administrative accounts could lead to further lateral movement or data breaches. This risk is heightened for public-facing websites with high traffic, including e-commerce, local business directories, and tourism-related sites that use Google Maps integrations. The integrity and confidentiality of user data and organizational information may be impacted, undermining trust and potentially violating GDPR if personal data is exposed. Although availability is not directly affected, reputational damage and remediation costs can be significant. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers often weaponize such vulnerabilities rapidly once disclosed.

Mitigation Recommendations

Immediate mitigation involves monitoring for plugin updates from the vendor and applying patches as soon as they are released. Until an official patch is available, organizations should restrict contributor-level permissions to trusted users only and audit existing content for suspicious shortcode usage. Implementing Web Application Firewall (WAF) rules to detect and block malicious payloads targeting the 'wpgsv_map' shortcode can reduce exploitation risk. Site administrators should enforce strict input validation and output encoding on shortcode parameters, potentially via custom plugin modifications or security plugins that sanitize inputs. Regular security reviews and user role audits will limit the attack surface. Additionally, enabling Content Security Policy (CSP) headers can help mitigate the impact of injected scripts by restricting script execution sources. Logging and monitoring web traffic for anomalous behavior related to shortcode usage can provide early detection. Finally, educating contributors about the risks of injecting untrusted content is recommended.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2026-01-01T22:54:23.480Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6960a320ecefc3cd7c0b9847

Added to database: 1/9/2026, 6:41:36 AM

Last enriched: 1/16/2026, 10:00:23 AM

Last updated: 2/21/2026, 11:47:22 AM

Views: 97

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats