Pods - Custom Content Types and Fields - Authenticated (Contributor+) Remote Code Execution
Strategic Overview
- Status
- Patched in 2.7.31.2
- Affected Plugin
- Pods – Custom Content Types and Fields
- Affected Version
2.7.31 – < 3.0.10.2 · 3 branches- CVSS
- 8.8High
- Weakness type
- CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')
- CVE
CVE-2023-6999
At a glance
CVE-2023-6999 is a high-severity Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in the Pods WordPress plugin, affecting versions 2.7.31 – < 3.0.10.2 · 3 branches. 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 Contributor level or above. The issue is fixed in version 2.7.31.2; sites on affected versions should update now. Disclosed March 2024, reported by Nex Team.
Vulnerability Overview
The Pods – Custom Content Types and Fields plugin for WordPress is vulnerable to Remote Code Exxecution via shortcode in all versions up to, and including, 3.0.10 (with the exception of 2.7.31.2, 2.8.23.2, 2.9.19.2). This makes it possible for authenticated attackers, with contributor level access or higher, to execute 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-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
Remediation
Update to one of the following versions, or a newer patched version: 2.7.31.2, 2.8.23.2, 2.9.19.2, 3.0.10.2
How does WordSec protect against this?
An attacker needs Contributor 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 2.7.31.2 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-2026-74851: Pods – Custom Content Types and Fields < 3.3.9.1 RCE
CVE-2026-74851 - 8.8CVE-2023-6967: Pods Custom Content Types and Fields - Authenticated
CVE-2023-6967 - 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