First published: Tue Apr 09 2024(Updated: )
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).
Credit: security@wordfence.com
Affected Software | Affected Version | How to fix |
---|---|---|
Pods Custom Content Types and Fields | <=3.0.10 | |
Pods Foundation | <2.7.31.2 | |
Pods Foundation | >=2.8<2.8.23.2 | |
Pods Foundation | >=2.9<2.9.19.2 | |
Pods Foundation | >=3.0.0<3.0.10.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-6965 is classified as a high-severity vulnerability due to missing authorization in the affected plugin.
To mitigate CVE-2023-6965, users should update the Pods – Custom Content Types and Fields plugin to version 3.0.11 or later.
CVE-2023-6965 affects all versions of the Pods plugin up to and including 3.0.10, with specific exceptions for versions 2.7.31.2, 2.8.23.2, and 2.9.19.2.
CVE-2023-6965 exploits a file inclusion feature in the plugin which does not implement proper authorization checks.
CVE-2023-6965 impacts WordPress installations using the Pods – Custom Content Types and Fields plugin.