Description
The CubeWP Framework WordPress plugin through 1.1.30 does not perform a per-object read authorization check, nor restrict which metadata keys may be requested, on one of its REST API endpoints, allowing users with the Contributor role and above to read arbitrary post metadata (including that of other users' draft, pending, private, and password-protected posts) and arbitrary user metadata of any user, including administrators.
Published: 2026-08-10
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The CVE arises from a missing authorization check on a REST API endpoint in CubeWP Framework through v1.1.30. An authenticated user with Contributor privileges or higher can query that endpoint for metadata keys without per-object read restrictions, allowing her to read any post’s metadata—including draft, pending, private, and password‑protected content—and any user’s metadata, including administrators. The flaw results in information disclosure to roles that normally should not have access to such data.

Affected Systems

Affected systems are installations of CubeWP Framework version 1.1.30 or earlier. The vulnerability is present whenever the plugin is active, regardless of the specific WordPress installation, because the code path is always reachable as part of the default API set. No specific WordPress version constraints are indicated, so all sites that have upgraded to 1.1.30 or earlier and have not applied a newer version are potentially exposed.

Risk and Exploitability

The likelihood of exploitation is facilitated by the fact that the API requires only standard authentication and does not perform per-object checks. A Contributor or Administrator account can invoke the endpoint and obtain sensitive data. Because the exploit does not need additional privileges, it can be carried out quickly by an internal actor. The EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog; however, the impact on confidentiality is substantial, so the risk remains high.

Generated by OpenCVE AI on August 10, 2026 at 07:29 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade CubeWP Framework to a version newer than 1.1.30.
  • Restrict access to the vulnerable REST API endpoint by firewall rules or .htaccess so that only trusted IP addresses can reach it, or block the endpoint entirely if it is not required.
  • Review and minimize user roles so that Contributors have no access to sensitive metadata, and remove unnecessary Contributor accounts if they are not needed.

Generated by OpenCVE AI on August 10, 2026 at 07:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 10 Aug 2026 07:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200
CWE-284

Mon, 10 Aug 2026 06:45:00 +0000

Type Values Removed Values Added
Description The CubeWP Framework WordPress plugin through 1.1.30 does not perform a per-object read authorization check, nor restrict which metadata keys may be requested, on one of its REST API endpoints, allowing users with the Contributor role and above to read arbitrary post metadata (including that of other users' draft, pending, private, and password-protected posts) and arbitrary user metadata of any user, including administrators.
Title CubeWP Framework <= 1.1.30 - Contributor+ Arbitrary Post and User Meta Disclosure via IDOR
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-08-10T06:00:13.787Z

Reserved: 2026-07-24T10:14:53.004Z

Link: CVE-2026-17018

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-10T07:30:14Z

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-284

    Improper Access Control