← WordPress Vulnerabilities
WordPress security by component

WP VR

WP VR is a WordPress component with 5 published CVE records in this archive. The latest tracked vulnerability was published Oct 21, 2024; the highest CVE/CNA score is 6.1.

Plugin slug: wp-vr

CVE-2024-49293: WP VR: A security weakness

WP VR is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

PublishedOct 21, 2024
Safe version guidanceSee mitigation notes
Safe version
Oct 21, 2024 CVE-2024-49293
WP VR: A security weakness
WP VR is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE4.3
NVD5.4
Jan 08, 2024 CVE-2023-6529
WP VR: Cross-site scripting
WP VR is affected by cross-site scripting. The vulnerable path is reachable without authentication. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.1
NVD6.1
Apr 24, 2023 CVE-2023-1414
WP VR: Cross-site request forgery
WP VR is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
See mitigation notes
CVE4.3
NVD4.3
Apr 17, 2023 CVE-2023-1413
WP VR: Cross-site scripting
WP VR is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.1
NVD6.1
Feb 06, 2023 CVE-2023-0174
WP VR: Cross-site scripting
WP VR is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE5.4
NVD5.4