# CVE-2026-17580: Missing authorization in Advanced Views – Display Custom Fields (ACF, Pods, MetaBox), Posts, CPT and Woo Products anywhere in Gutenberg, Elementor, Divi, Beaver…

> Authenticated subscribers can access sensitive admin-authored editor content via unprotected REST endpoints in the Advanced Views WordPress plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-wfv8-4fgp-fr6r

## What is CVE-2026-17580?

CVE-2026-17580 is a medium-severity missing authorization vulnerability in wplakeorg Advanced Views – Display Custom Fields (ACF, Pods, MetaBox), Posts, CPT and Woo Products anywhere in Gutenberg, Elementor, Divi, Beaver…, published on 1 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Advanced Views – Display Custom Fields (ACF, Pods, MetaBox), Posts, CPT and Woo Products anywhere in Gutenberg, Elementor, Divi, Beaver… plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.9.1 via the register_rest_routes. This makes it possible for authenticated attackers, with subscriber-level access and above, to extract sensitive admin-authored editor content — including template markup, CSS code, JavaScript code, and PHP controller variables — for any Layout or Post Selection post on the site.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-17580?


## How do I fix CVE-2026-17580?

No fix has been published for CVE-2026-17580 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-17580 being exploited?

There is no known exploitation of CVE-2026-17580 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-17580 and fix it if it is affected.

What it is: CVE-2026-17580 is a medium-severity missing authorization vulnerability in wplakeorg Advanced Views – Display Custom Fields (ACF, Pods, MetaBox), Posts, CPT and Woo Products anywhere in Gutenberg, Elementor, Divi, Beaver…, published on 1 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-17580 in the wild and no public exploit code.

Affected product: wplakeorg Advanced Views – Display Custom Fields (ACF, Pods, MetaBox), Posts, CPT and Woo Products anywhere in Gutenberg, Elementor, Divi, Beaver…. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-17580/ (Markdown: https://insights.sbomify.com/CVE-2026-17580/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-17580
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-17580
- OSV: https://osv.dev/vulnerability/CVE-2026-17580

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-17580/
Summaries are generated and may contain mistakes; the official description above is the record.