Pods <= 3.3.9 - Unauthenticated Privilege Escalation via Authorization Bypass to Admin Methods via 'pods_admin' AJAX Router
Strategic Overview
- Status
- Patched in 2.8.23.4
- Affected Plugin
- Pods – Custom Content Types and Fields
- Affected Version
2.8 – 3.3.9 · 6 branches- CVSS
- 9.8Critical
- Weakness type
- CWE-863 · Incorrect Authorization
- CVE
CVE-2026-19598
At a glance
CVE-2026-19598 is a critical-severity Incorrect Authorization vulnerability in the Pods WordPress plugin, affecting versions 2.8 – 3.3.9 · 6 branches. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.8.23.4; sites on affected versions should update now. Disclosed August 2026, reported by Nhien Pham (nhienit).
Vulnerability Overview
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.
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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-863: Incorrect Authorization
Pods 2.8 – 3.3.9 · 6 branches carries this weakness at pods_error(), and reaching it takes no account at all. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.
The action runs for users the code intended to exclude, with the same effect as having no check at all. For Pods the fix is 2.8.23.4: builds 2.8 – 3.3.9 · 6 branches are affected, anything from 2.8.23.4 onward is not.
Remediation
Update to one of the following versions, or a newer patched version: 2.8.23.4, 2.9.19.4, 3.0.10.4, 3.1.4.2, 3.2.8.3, 3.3.9.1
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Pods 2.8.23.4 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.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-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 - 7.1CVE-2023-23790: Pods <= 2.9.10.2 Cross-Site Request Forgery
CVE-2023-23790 - 6.1CVE-2014-7956: Pods <= 2.4.3 Cross-Site Scripting
CVE-2014-7956
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C