HomeWordPress vulnerabilitiesPods
Pods vulnerabilities
Pods has 15 known vulnerabilities in this database. The most recent published record is dated 5 Sep 2026.
- Known vulnerabilities
- 15
- Active installs
- 100,000+
- Latest version
- 3.3.9.2
- Last updated
- 31 Aug 2026
- Most recent
- 5 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-76573 | Medium 6.4 | Up to 3.3.9.1 | Fixed in a later version (latest 3.3.9.2) | 5 Sep 2026 |
| Security weakness CVE-2026-74853 | Medium 6.8 | Before 3.3.9.2 | Fixed in 3.3.9.2 | 4 Sep 2026 |
| Remote code execution CVE-2026-74851 | High 7.2 | Before 3.3.9.1 | Fixed in 3.3.9.1 | 26 Aug 2026 |
| Privilege escalation CVE-2026-19598 | Critical 9.8 | Up to 3.3.9 | Fixed in a later version (latest 3.3.9.2) | 15 Aug 2026 |
| SQL injection CVE-2025-1446 | Critical 9.8 | Before 3.2.8.2 | Fixed in 3.2.8.2 | 23 Mar 2025 |
| Cross-site scripting (XSS) CVE-2024-11849 | Medium 6.1 | Before 3.2.8.1 | Fixed in 3.2.8.1 | 6 Jan 2025 |
| Cross-site scripting (XSS) CVE-2024-9883 | Medium 4.8 | Before 3.2.7.1 | Fixed in 3.2.7.1 | 5 Nov 2024 |
| Cross-site scripting (XSS) CVE-2024-3956 | Medium 5.4 | Up to 3.2.1 | Fixed in a later version (latest 3.3.9.2) | 14 May 2024 |
| Broken access control CVE-2023-6965 | Medium 4.3 | Before 3.0.10.2 | Fixed in 3.0.10.2 | 9 Apr 2024 |
| SQL injection CVE-2023-6967 | High 8.8 | Before 3.0.10.2 | Fixed in 3.0.10.2 | 9 Apr 2024 |
| Remote code execution CVE-2023-6999 | High 8.8 | Before 3.0.10.2 | Fixed in 3.0.10.2 | 9 Apr 2024 |
| Cross-site scripting (XSS) CVE-2021-24338 | Medium 5.4 | Before 2.7.27 | Fixed in 2.7.27 | 21 Jun 2021 |
| Cross-site scripting (XSS) CVE-2021-24339 | Medium 5.4 | Before 2.7.27 | Fixed in 2.7.27 | 21 Jun 2021 |
| Cross-site scripting (XSS) CVE-2014-7957 | Not scored | Up to 2.4.3 | Fixed in a later version (latest 3.3.9.2) | 15 Jan 2015 |
| Cross-site scripting (XSS) CVE-2014-7956 | Not scored | Up to 2.4.3 | Fixed in a later version (latest 3.3.9.2) | 15 Jan 2015 |
Read the published descriptions
- CVE-2026-76573, 5 Sep 2026
- The Pods - Custom Content Types and Fields plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'not_found' Shortcode Attribute in all versions up to, and including, 3.3.9.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2026-74853, 4 Sep 2026
- The Pods WordPress plugin before 3.3.9.2 does not restrict which functions a display callback may resolve to, allowing users with the author role and above to read arbitrary files from the server, including files outside the web root. Only sites using the restricted display-callback mode are affected, which is the automatic default on installations whose first Pods version predates 3.1. CVE record
- CVE-2026-74851, 26 Aug 2026
- The Pods WordPress plugin before 3.3.9.1 does not correctly compare a display callback against its list of blocked functions, allowing users with the author role and above to execute arbitrary code on the server. Only sites using the restricted display-callback mode are affected, which is the automatic default on installations whose first Pods version predates 3.1. CVE record
- CVE-2026-19598, 15 Aug 2026
- The Pods - Custom Content Types and Fields plugin for WordPress is vulnerable to Privilege Escalation via Authorization Bypass in all versions up to, and including, 3.3.9. The vulnerability exists because the pods_admin AJAX router funnels every access check - including the method allowlist, nonce verification, login enforcement, and capability gate - through pods_error(), which under the JSON meta-box-loader compatibility path only writes failures to the PHP error log and returns false instead of terminating the request, rendering all guards ineffective. This makes it possible for unauthenticated attackers to escalate their privileges to Administrator or overwrite the password of any user account, including the site owner's, enabling complete site takeover, or perform another administrator action. CVE record
- CVE-2025-1446, 23 Mar 2025
- The Pods WordPress plugin before 3.2.8.2 does not sanitize and escape a parameter before using it in a SQL statement, allowing admins to perform SQL injection attacks CVE record
- CVE-2024-11849, 6 Jan 2025
- The Pods WordPress plugin before 3.2.8.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup). CVE record
- CVE-2024-9883, 5 Nov 2024
- The Pods WordPress plugin before 3.2.7.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup). CVE record
- CVE-2024-3956, 14 May 2024
- The Pods - Custom Content Types and Fields plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Pod Form widget in all versions up to, and including, 3.2.1 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2023-6965, 9 Apr 2024
- 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). CVE record
- CVE-2023-6967, 9 Apr 2024
- The Pods - Custom Content Types and Fields plugin for WordPress is vulnerable to SQL Injection 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) due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with contributor level access or higher, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. CVE record
- CVE-2023-6999, 9 Apr 2024
- 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. CVE record
- CVE-2021-24338, 21 Jun 2021
- The Pods - Custom Content Types and Fields WordPress plugin before 2.7.27 was vulnerable to an Authenticated Stored Cross-Site Scripting (XSS) security vulnerability within the 'Singular Label' field parameter. CVE record
- CVE-2021-24339, 21 Jun 2021
- The Pods - Custom Content Types and Fields WordPress plugin before 2.7.27 was vulnerable to an Authenticated Stored Cross-Site Scripting (XSS) security vulnerability within the 'Menu Label' field parameter. CVE record
- CVE-2014-7957, 15 Jan 2015
- Multiple cross-site request forgery (CSRF) vulnerabilities in the Pods plugin before 2.5 for WordPress allow remote attackers to hijack the authentication of administrators for requests that (1) conduct cross-site scripting (XSS) attacks via the toggled parameter in a toggle action in the pods-components page to wp-admin/admin.php, (2) delete a pod in a delete action in the pods page to wp-admin/admin.php, (3) reset pod settings and data via the pods_reset parameter in the pod-settings page to wp-admin/admin.php, (4) deactivate and reset pod data via the pods_reset_deactivate parameter in the pod-settings page to wp-admin/admin.php, (5) delete the admin role via the id parameter in a delete action in the pods-component-roles-and-capabilities page to wp-admin/admin.php, or (6) enable "roles and capabilities" in a toggle action in the pods-components page to wp-admin/admin.php. CVE record
- CVE-2014-7956, 15 Jan 2015
- Cross-site scripting (XSS) vulnerability in the Pods plugin before 2.5 for WordPress allows remote attackers to inject arbitrary web script or HTML via the id parameter in an edit action in the pods page to wp-admin/admin.php. CVE record
What to do if you run Pods
If you run Pods, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Pods vulnerabilities
Free. We email you when a new vulnerability is published for Pods, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.