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
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2023-6965
At a glance
CVE-2023-6965 is a medium-severity Missing Authorization vulnerability in the Pods WordPress plugin, affecting versions 2.7.31 – < 3.0.10.2 · 3 branches. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. 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 Missing Authorization 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 is due to the fact that the plugin allows the use of a file inclusion feature via shortcode. This makes it possible for authenticated attackers, with contributor access or higher, to create pods and users (with default role).
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.
CWE-862: Missing Authorization
Reaching this weakness in Pods 2.7.31 – < 3.0.10.2 · 3 branches takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Pods the fix is 2.7.31.2: builds 2.7.31 – < 3.0.10.2 · 3 branches are affected, anything from 2.7.31.2 onward is not.
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?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Pods 2.7.31.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- 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 - 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
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C