CVE-2026-8682

3D Viewer <= 2.0.1 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Plugin Settings Modification via settings REST endpoint

2026-05-27 00:00
Legion Hunter

Strategic Overview

Status
Patched in 2.0.2
Affected Version
<= 2.0.1
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-8682
View all 3D Viewer – 3D Model Viewer – Augmented Reality – Virtual Try On vulnerabilities

At a glance

CVE-2026-8682 is a medium-severity Missing Authorization vulnerability in the 3D Viewer WordPress plugin, affecting versions <= 2.0.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.0.2; sites on affected versions should update now. Disclosed May 2026, reported by Legion Hunter.

Vulnerability Overview

The 3D Viewer – 3D Model Viewer – Augmented Reality – Virtual Try On plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.0.1. 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 subscriber-level access and above, to modify all plugin settings by writing arbitrary data to the ar_try_on_settings option in the database via the /wp-json/ar_try_on/v1/settings REST endpoint.

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-862: Missing Authorization

Reaching this weakness in 3D Viewer <= 2.0.1 takes an account at Subscriber level or above. 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 3D Viewer the fix is 2.0.2: builds <= 2.0.1 are affected, anything from 2.0.2 onward is not.

Remediation

Update to version 2.0.2, 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: 3D Viewer 2.0.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

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