CVE-2023-6529

WP VR <= 8.3.14 - Missing Authorization to Plugin Version Downgrade

2023-12-14 00:00
Krzysztof Zając

Strategic Overview

Status
Patched in 8.3.15
Affected Plugin
WP VR – 360 Panorama and Virtual Tour Builder
Affected Version
<= 8.3.14
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-6529
View all WP VR – 360 Panorama and Virtual Tour Builder vulnerabilities

At a glance

CVE-2023-6529 is a medium-severity Missing Authorization vulnerability in the WP VR WordPress plugin, affecting versions <= 8.3.14. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 8.3.15; sites on affected versions should update now. Disclosed December 2023, reported by Krzysztof Zając.

Vulnerability Overview

The WP VR – 360 Panorama and Virtual Tour Builder For WordPress plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the trigger_rollback() function in all versions up to, and including, 8.3.14. This makes it possible for unauthenticated attackers to downgrade the plugins version which can be used to exploit older vulnerabilities.

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, and no interaction from a victim user.

CWE-862: Missing Authorization

WP VR <= 8.3.14 carries this weakness at trigger_rollback(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WP VR the fix is 8.3.15: builds <= 8.3.14 are affected, anything from 8.3.15 onward is not.

Remediation

Update to version 8.3.15, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP VR 8.3.15 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-6529https://www.wordfence.com/threat-intel/vulnerabilities/id/34fcc835-593f-435b-ad00-07ca0cb649fahttps://nvd.nist.gov/vuln/detail/CVE-2023-6529

Related records

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