CVE-2023-25708

WP VR <= 8.2.7 - Cross-Site Request Forgery

2023-02-14 00:00
Abdi Pranata

Strategic Overview

Status
Patched in 8.2.8
Affected Plugin
WP VR – 360 Panorama and Virtual Tour Builder
Affected Version
<= 8.2.7
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-25708
View all WP VR – 360 Panorama and Virtual Tour Builder vulnerabilities

At a glance

CVE-2023-25708 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP VR WordPress plugin, affecting versions <= 8.2.7. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 8.2.8; sites on affected versions should update now. Disclosed February 2023, reported by Abdi Pranata.

Vulnerability Overview

The WP VR plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 8.2.7. This is due to missing or incorrect nonce validation on the 'wpvr_role_management' function. This makes it possible for unauthenticated attackers to change plugin settings, including granting author-level users the ability to create VR tours, via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

WP VR <= 8.2.7 carries this weakness at wpvr_role_management, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WP VR the fix is 8.2.8: builds <= 8.2.7 are affected, anything from 8.2.8 onward is not.

Remediation

Update to version 8.2.8, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WP VR: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP VR 8.2.8 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-25708https://www.wordfence.com/threat-intel/vulnerabilities/id/13a0dd72-1124-4b5d-9bad-fe4fea8e3e68https://nvd.nist.gov/vuln/detail/CVE-2023-25708

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C