Advanced Views – Display Posts, Custom Fields, and More <= 3.7.19 - Authenticated (Author+) Remote Code Execution via SSTI
Strategic Overview
- Status
- Patched in 3.7.20
- Affected Plugin
- Advanced Views – Display Framework for Gutenberg & Elementor
- Affected Version
<= 3.7.19- CVSS
- 8.8High
- Weakness type
- CWE-1336 · Improper Neutralization of Special Elements Used in a Template Engine
- CVE
CVE-2025-10380
At a glance
CVE-2025-10380 is a high-severity Improper Neutralization of Special Elements Used in a Template Engine vulnerability in the Advanced Views WordPress plugin, affecting versions <= 3.7.19. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 3.7.20; sites on affected versions should update now. Disclosed September 2025, reported by Aurélien BOURDOIS (Elymaro).
Vulnerability Overview
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.
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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine
The product uses a template engine to insert or process externally-influenced input, but it does not neutralize or incorrectly neutralizes special elements or syntax that can be interpreted as template expressions or other code directives when processed by the engine.
Remediation
Update to version 3.7.20, or a newer patched version
How does WordSec protect against this?
An attacker needs Author access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Advanced Views 3.7.20 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Other vulnerabilities in Advanced Views – Display Framework for Gutenberg & Elementor
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C