Authenticated code execution via unchecked snippet update
Published Jan 8, 2025 · Updated Apr 8, 2026
Remote code execution in WP Extended 3.0.11 and earlier allows remote authenticated users to execute PHP code via a snippet update. The wpext_handle_snippet_update function accepts snippet-content changes without checking the caller's capabilities, so a Subscriber can replace trusted snippet code. Exploitation requires Subscriber-level access and at least one snippet previously created by an administrator; the injected code then runs on the WordPress server.
Summary
What happened
Remote code execution in WP Extended 3.0.11 and earlier allows remote authenticated users to execute PHP code via a snippet update. The wpext_handle_snippet_update function accepts snippet-content changes without checking the caller's capabilities, so a Subscriber can replace trusted snippet code. Exploitation requires Subscriber-level access and at least one snippet previously created by an administrator; the injected code then runs on the WordPress server.
The record
- CVE
- CVE-2024-11816
- Published
- Jan 8, 2025
- Updated
- Apr 8, 2026
- Vendor
- WP Extended
- Product
- WP Extended – The Ultimate WordPress Toolkit
- Classifications
- CWE-862, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 8, 2025CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=3.0.11
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo