WordPress plugin · Updated daily · Source: Wordfence Intelligence

Pods vulnerabilities: affected versions and fixes

Pods has 100,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Pods at a glance

  • 20 publicly disclosed vulnerabilities, 9 of them rated High or Critical. The most recent was disclosed on Sep 4, 2026.
  • Ranked #405 by popularity on WordPress.org (100,000+ active installs).
  • The latest version is 3.3.9.2 (released Aug 31, 2026). The most recent security fix shipped in 3.3.9.2.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your Pods version

Enter the Pods version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “Pods”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Pods”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (3.3.9.2). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Pods vulnerabilities

  • Pods – Custom Content Types and Fields 3.3 - 3.3.9.1 - Authenticated (Author+) Arbitrary File Read

    Arbitrary file read or deletion · CVE-2026-74853

    Affected versions: ≥ 3.3, ≤ 3.3.9.1

    Fixed in: 3.3.9.2

    Severity: Medium 6.5 · Disclosed Sep 4, 2026

  • Pods <= 3.3.9.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'not_found' Shortcode Attribute

    Cross-site scripting (XSS) · CVE-2026-76573

    Affected versions: ≤ 3.3.9.1

    Fixed in: 3.3.9.2

    Severity: Medium 6.4 · Disclosed Sep 4, 2026

  • Pods – Custom Content Types and Fields < 3.3.9.1 - Authenticated (Author+) Remote Code Execution

    Remote code execution · CVE-2026-74851

    Affected versions: < 3.3.9.1

    Fixed in: 3.3.9.1

    Severity: High 8.8 · Disclosed Aug 28, 2026

  • Pods <= 3.3.9 - Unauthenticated Privilege Escalation via Authorization Bypass to Admin Methods via 'pods_admin' AJAX Router

    Privilege escalation · CVE-2026-19598

    Affected versions: ≥ 3.1, ≤ 3.1.4.1

    Fixed in: 2.8.23.4, 2.9.19.4, 3.0.10.4, 3.1.4.2, 3.2.8.3, 3.3.9.1

    Severity: Critical 9.8 · Disclosed Aug 15, 2026

  • Pods – Custom Content Types and Fields <= 3.3.8 - Unauthenticated Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2026-54191

    Affected versions: ≤ 3.3.8

    Fixed in: 3.3.9

    Severity: High 7.2 · Disclosed Jun 15, 2026

  • Pods – Custom Content Types and Fields <= 3.2.8.1 - Authenticated (Admin+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2025-1446

    Affected versions: ≤ 3.2.8.1

    Fixed in: 3.2.8.2

    Severity: Medium 4.4 · Disclosed Mar 2, 2025

  • Pods – Custom Content Types and Fields <= 3.2.8 - Authenticated (Admin+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-11849

    Affected versions: ≤ 3.2.8

    Fixed in: 3.2.8.1

    Severity: Medium 4.4 · Disclosed Dec 16, 2024

  • Pods <= 3.2.7 - Authenticated (Administrator+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-9883

    Affected versions: ≤ 3.2.7

    Fixed in: 3.2.7.1

    Severity: Medium 4.4 · Disclosed Oct 15, 2024

  • Several WordPress.org Plugins <= Various Versions - Injected Backdoor

    Other weakness · CVE-2024-6297

    Affected versions: ≥ 3.2.3, ≤ 3.2.3

    Fixed in: 3.2.4

    Severity: Critical 10 · Disclosed Jun 24, 2024

  • Pods – Custom Content Types and Fields <= 3.2.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via Pod Form Redirect URL

    Cross-site scripting (XSS) · CVE-2024-3956

    Affected versions: ≤ 3.2.1

    Fixed in: 3.2.1.1

    Severity: Medium 5.4 · Disclosed May 9, 2024

  • Pods - Custom Content Types and Fields - Missing Authorization

    Missing authorization · CVE-2023-6965

    Affected versions: ≥ 3, < 3.0.10.2

    Fixed in: 2.7.31.2, 2.8.23.2, 2.9.19.2, 3.0.10.2

    Severity: Medium 4.3 · Disclosed Mar 28, 2024

  • Pods - Custom Content Types and Fields - Authenticated (Contributor+) Remote Code Execution

    Remote code execution · CVE-2023-6999

    Affected versions: ≥ 2.8, < 2.8.23.2

    Fixed in: 2.7.31.2, 2.8.23.2, 2.9.19.2, 3.0.10.2

    Severity: High 8.8 · Disclosed Mar 28, 2024

  • Pods - Custom Content Types and Fields - Authenticated (Contributor+) SQL Injection via Shortcode

    SQL injection · CVE-2023-6967

    Affected versions: < 2.7.31

    Fixed in: 2.7.31.2, 2.8.23.2, 2.9.19.2, 3.0.10.2

    Severity: High 8.8 · Disclosed Mar 28, 2024

  • Pods <= 2.9.10.2 - Cross-Site Request Forgery

    Cross-site request forgery (CSRF) · CVE-2023-23790

    Affected versions: ≤ 2.9.10.2

    Fixed in: 2.9.11

    Severity: High 7.1 · Disclosed Jan 20, 2023

  • Pods – Custom Content Types and Fields <= 2.7.28 - Authenticated (Admin+) Cross-Site Scripting

    Cross-site scripting (XSS)

    Affected versions: ≤ 2.7.28

    Fixed in: 2.7.29

    Severity: Medium 5.5 · Disclosed Aug 6, 2021

  • Pods 2.4.4.1 - 2.7.26 - Authenticated Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2021-24338

    Affected versions: ≥ 2.4.4.1, < 2.7.27

    Fixed in: 2.7.27

    Severity: Medium 5.4 · Disclosed Jan 15, 2021

  • Pods <= 2.7.26 - Authenticated Stored Cross-Site Scripting via Menu Label field

    Cross-site scripting (XSS) · CVE-2021-24339

    Affected versions: ≥ 2.4.4.2, ≤ 2.7.26

    Fixed in: 2.7.27

    Severity: Medium 5.4 · Disclosed Jan 15, 2021

  • Pods – Custom Content Types and Fields < 2.5.1.2 - SQL Injection

    SQL injection

    Affected versions: < 2.5.1.2

    Fixed in: 2.5.1.2

    Severity: Critical 9.8 · Disclosed Mar 16, 2015

  • Pods <= 2.4.3 - Multiple Cross-Site Request Forgery

    Cross-site request forgery (CSRF) · CVE-2014-7957

    Affected versions: ≤ 2.4.3

    Fixed in: 2.5

    Severity: Critical 9.6 · Disclosed Jan 12, 2015

  • Pods <= 2.4.3 - Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2014-7956

    Affected versions: ≤ 2.4.3

    Fixed in: 2.5

    Severity: Medium 6.1 · Disclosed Jan 12, 2015

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Sep 4, 2026.

Most common weaknesses in Pods

Cross-site scripting (XSS)

10 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Remote code execution

2 issues

An attacker can run code of their choice on your server. This is the most dangerous kind: it usually means a full takeover of the site.

SQL injection

2 issues

Input such as a form field can be used to rewrite the queries the site sends to its database. Attackers use it to pull out customer, member or order data.

Frequently asked questions

Is Pods safe to use?

Pods is a well-known plugin with 100,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (3.3.9.2) and turn on automatic updates.

How do I find which version of Pods my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesPods on WordPress.org