CVE-2025-12005

WP VR – 360 Panorama and Free Virtual Tour Builder For WordPress <= 8.5.41 - Improper Authorization to Authenticated (Contributor+) Plugin Settings Update

2025-10-24 16:51
Rafshanzani Suhada

Strategic Overview

Status
Patched in 8.5.42
Affected Plugin
WP VR – 360 Panorama and Virtual Tour Builder
Affected Version
<= 8.5.41
CVSS
4.3Medium
Weakness type
CWE-285 · Improper Authorization
CVE
CVE-2025-12005
View all WP VR – 360 Panorama and Virtual Tour Builder vulnerabilities

At a glance

CVE-2025-12005 is a medium-severity Improper Authorization vulnerability in the WP VR WordPress plugin, affecting versions <= 8.5.41. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 8.5.42; sites on affected versions should update now. Disclosed October 2025, reported by Rafshanzani Suhada.

Vulnerability Overview

The WP VR – 360 Panorama and Free Virtual Tour Builder For WordPress plugin for WordPress is vulnerable to unauthorized access of data in all versions up to, and including, 8.5.41. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor level access and above, to modify sensitive plugin options.

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

CWE-285: Improper Authorization

Reaching this weakness in WP VR <= 8.5.41 takes an account at Contributor level or above. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.

A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For WP VR the fix is 8.5.42: builds <= 8.5.41 are affected, anything from 8.5.42 onward is not.

Remediation

Update to version 8.5.42, 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.5.42 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-12005https://www.wordfence.com/threat-intel/vulnerabilities/id/9bcbc0cf-69e5-4d6e-8987-a0fbbaf41740https://nvd.nist.gov/vuln/detail/CVE-2025-12005

Related records

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