WordPress Pods plugin: unauthenticated privilege escalation via AJAX auth bypass
Pods WordPress plugin (≤3.3.9): an AJAX authorization bypass silently swallows auth failures via pods_error(), allowing unauthenticated privilege escalation on affected sites.
- Vendor
- Pods Framework
- Product
- Pods – Custom Content Types and Fields WordPress Plugin (all versions through 3.3.9)
- CVSS
- 9.8
- EPSS (exploit probability)
- 3.5%
- Status
- patched
- Published
Is CVE-2026-19598 being exploited?
Not on any exploited-vulnerability catalog we track. CVE-2026-19598 was not on the CISA, ENISA or CIRCL exploited catalogs as of our 2026-11-22 snapshot. That can change quickly; check the write-up below for the latest reporting.
FIRST's EPSS model puts the probability of exploitation activity in the next 30 days at 3.5% (scored November 8, 2026).
- CISA KEV[ — ]
- ENISA EUVD (exploited)[ — ]
- CIRCL KEV[ — ]
Catalog snapshot 2026-11-22. Full cross-catalog view: /kev-comparison
CVE-2026-19598 timeline
Every event links to its source. Catalog dates are each catalog's own; day offsets count from NVD publication. Data: JSON
The Pods plugin routes admin AJAX actions through the pods_admin AJAX router, which funnels every access check — login enforcement, capability gates, nonce verification — through pods_error(). Under the JSON meta-box-loader compatibility path, pods_error() writes failures to the PHP error log and returns false rather than halting execution. Downstream access checks complete regardless. An unauthenticated attacker can trigger privileged operations through this path without valid credentials.
Affected versions: All Pods releases through 3.3.9.
Patch: Update Pods to the latest available version via the WordPress plugin directory. Sites running Pods as core infrastructure for custom post types should prioritize this — the AJAX surface this flaw exposes is likely active in any non-trivial Pods deployment.
NVD record: CVE-2026-19598
