CVE-2026-16966

Solace Extra < 1.7.0 - Missing Authorization to Unauthenticated Unpublished Site Builder Content Disclosure

2026-08-31 00:00
JunHee CHO

Strategic Overview

Status
Patched in 1.7.0
Affected Plugin
Solace Extra
Affected Version
< 1.7.0
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-16966
View all Solace Extra vulnerabilities

At a glance

CVE-2026-16966 is a medium-severity Missing Authorization vulnerability in the Solace Extra WordPress plugin, affecting versions < 1.7.0. 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 1.7.0; sites on affected versions should update now. Disclosed August 2026, reported by JunHee CHO.

Vulnerability Overview

The Solace Extra plugin for WordPress is vulnerable to unauthorized access in all versions up to 1.7.0. This is due to missing post-status and capability checks on the Site Builder part rendering endpoint, which previously served any solace-sitebuilder post regardless of publication status or user identity. This makes it possible for unauthenticated attackers to read the full rendered content of non-published (draft, pending, private, or trashed) Site Builder parts without authentication.

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

Reaching this weakness in Solace Extra < 1.7.0 takes no account at all. 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 Solace Extra the fix is 1.7.0: builds < 1.7.0 are affected, anything from 1.7.0 onward is not.

Remediation

Update to version 1.7.0, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Solace Extra 1.7.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-16966https://www.wordfence.com/threat-intel/vulnerabilities/id/0274f1c0-aae5-4f5d-9ce3-de93326c1d69https://nvd.nist.gov/vuln/detail/CVE-2026-16966

Related records

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