What is the CVSS score of CVE-2025-6350?

CVE-2025-6350 has a CVSS 3.1 base score of 6.4 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.0%.

Which versions of Wp Vr are affected by CVE-2025-6350?

Organizations using all should be aware of moderate risk from CVE-2025-6350, a cross-site scripting vulnerability rated CVSS 6.4.. A patch is available.

How to fix or mitigate CVE-2025-6350?

Within 30 days: Identify affected systems running all and apply vendor patches as part of regular patch cycle. Verify Content-Security-Policy and output encoding.

Wp Vr CVE-2025-6350

EUVD-2025-28724 MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2025-06-28 security@wordfence.com

WordPress XSS Wp Vr PHP

6.4

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

6.4 MEDIUM

AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

EUVD ID Assigned

Mar 16, 2026 - 01:05 euvd

EUVD-2025-28724

Analysis Generated

Mar 16, 2026 - 01:05 vuln.today

Patch released

Mar 16, 2026 - 01:05 nvd

Patch available

CVE Published

Jun 28, 2025 - 04:15 nvd

MEDIUM 6.4

DescriptionCVE.org

The WP VR - 360 Panorama and Free Virtual Tour Builder For WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘hotspot-hover’ parameter in all versions up to, and including, 8.5.32 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Analysis

Technical ContextAI

Cross-site scripting (XSS) allows injection of client-side scripts into web pages viewed by other users due to insufficient output encoding.

RemediationAI

A vendor patch is available — apply it immediately. Encode all user-supplied output contextually (HTML, JS, URL). Implement Content Security Policy (CSP) headers. Use HTTPOnly and Secure cookie flags.