# CVE-2025-10380: Code injection in Advanced Views – Display Custom Fields (ACF, Pods, MetaBox), Posts, CPT and Woo Products anywhere in Gutenberg, Elementor, Divi, Beaver…

> Authenticated attackers with author-level access can execute arbitrary PHP code via Server-Side Template Injection in the Advanced Views WordPress plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 23 Sep 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-57cg-6gv7-xf26

## What is CVE-2025-10380?

CVE-2025-10380 is a high-severity code injection vulnerability in wplakeorg Advanced Views – Display Custom Fields (ACF, Pods, MetaBox), Posts, CPT and Woo Products anywhere in Gutenberg, Elementor, Divi, Beaver…, published on 23 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Advanced Views – Display Posts, Custom Fields, and More plugin for WordPress is vulnerable to Server-Side Template Injection in all versions up to, and including, 3.7.19. This is due to insufficient input sanitization and lack of access control when processing custom Twig templates in the Model panel. This makes it possible for authenticated attackers, with author-level access or higher, to execute arbitrary PHP code and commands on the server.

Weakness: CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

## Which versions are affected by CVE-2025-10380?


## How do I fix CVE-2025-10380?

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

## Is CVE-2025-10380 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10380 and fix it if it is affected.

What it is: CVE-2025-10380 is a high-severity code injection vulnerability in wplakeorg Advanced Views – Display Custom Fields (ACF, Pods, MetaBox), Posts, CPT and Woo Products anywhere in Gutenberg, Elementor, Divi, Beaver…, published on 23 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10380 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-2025-10380/ (Markdown: https://insights.sbomify.com/CVE-2025-10380/index.md)
```

## Sources

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

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