Pods – Custom Content Types and Fields < 3.3.9.1 - Authenticated (Author+) Remote Code Execution
Strategic Overview
- Status
- Patched in 3.3.9.1
- Affected Plugin
- Pods – Custom Content Types and Fields
- Affected Version
< 3.3.9.1- CVSS
- 8.8High
- Weakness type
- CWE-94 · Improper Control of Generation of Code ('Code Injection')
- CVE
CVE-2026-74851
At a glance
CVE-2026-74851 is a high-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Pods WordPress plugin, affecting versions < 3.3.9.1. 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.3.9.1; sites on affected versions should update now. Disclosed August 2026, reported by Tyler Chin.
Vulnerability Overview
The Pods – Custom Content Types and Fields plugin for WordPress is vulnerable to Remote Code Execution in all versions up to 3.3.9.1. This is due to insufficient validation of user supplied input before it is executed. This makes it possible for authenticated attackers, with author-level access and above, to execute arbitrary code 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-94: Improper Control of Generation of Code ('Code Injection')
Reaching this weakness in Pods < 3.3.9.1 takes an account at Author level or above. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.
The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For Pods the fix is 3.3.9.1: builds < 3.3.9.1 are affected, anything from 3.3.9.1 onward is not.
Remediation
Update to version 3.3.9.1, 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: Pods 3.3.9.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Other vulnerabilities in Pods – Custom Content Types and Fields
- 10.0CVE-2024-6297: Several WordPress.org Plugins <=… Injected Backdoor
CVE-2024-6297 - 9.8CVE-2026-19598: Pods <= 3.3.9 Privilege Escalation
CVE-2026-19598 - 9.8Pods – Custom Content Types and Fields < 2.5.1.2 SQL Injection
- 9.6CVE-2014-7957: Pods <= 2.4.3 Multiple Cross-Site Request Forgery
CVE-2014-7957 - 8.8CVE-2023-6967: Pods Custom Content Types and Fields - Authenticated
CVE-2023-6967 - 8.8CVE-2023-6999: Pods Custom Content Types and Fields - Authenticated
CVE-2023-6999 - 7.2CVE-2026-54191: Pods – Custom Content Types and Fields Stored XSS
CVE-2026-54191 - 7.1CVE-2023-23790: Pods <= 2.9.10.2 Cross-Site Request Forgery
CVE-2023-23790
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C