On this page

Atomicorp WAF Research Note: CVE-2026-19598

Pods <= 3.3.9 - Unauthenticated Privilege Escalation via pods_admin AJAX Router

CVE Details

Status: Detected by Atomicorp
  • Already protected by existing Atomicorp WAF rules
  • Protection status: Understanding Atomicorp WAF Protection Status
  • CVE: CVE-2026-19598
  • Name: Pods <= 3.3.9 - Unauthenticated Privilege Escalation via pods_admin AJAX Router
  • Severity: Critical
  • CVSS: 9.8 (v3.1) (Critical)
  • CVSS version: 3.1
  • CVSS source: Wordfence CNA
  • CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
    • Attack vector: Network
    • Attack complexity: Low
    • Privileges required: None
    • User interaction: None
    • Scope: Unchanged
    • Confidentiality impact: High
    • Integrity impact: High
    • Availability impact: High
  • CWE: CWE-863 — Incorrect Authorization
  • Vendor: podsfoundation
  • Vulnerable products: Pods – Custom Content Types and Fields , pods
  • CVE published: 2026-08-15
  • CVE last modified: 2026-08-20
  • EPSS: 0.0279; 85.6th percentile (FIRST )
  • Latest Update: 2026-08-25
  • Selected Rule IDs observed: 377360
  • Matching rules: 1; rules with blocking actions: 0
  • Would-block Rule IDs: N/A

Vulnerability Description

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.

  1. Maintain the observed Atomicorp detections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (377360 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings. These observations are detection-only; review the resulting events and do not assume they block exploitation.

  2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

    • Affected versions: sc0ttkclark Pods – Custom Content Types and Fields versions through 2.8.23.3.
    • Affected versions: sc0ttkclark Pods – Custom Content Types and Fields versions through 2.9.19.3.
    • Affected versions: sc0ttkclark Pods – Custom Content Types and Fields versions through 3.0.10.3.
    • Affected versions: sc0ttkclark Pods – Custom Content Types and Fields versions through 3.1.4.1.
    • Affected versions: sc0ttkclark Pods – Custom Content Types and Fields versions through 3.2.8.2.
    • Affected versions: sc0ttkclark Pods – Custom Content Types and Fields versions through 3.3.9.
    • No specific CNA/vendor solution or workaround is included in the current CVE Record . Review the vendor’s security advisories and supported-release guidance before making changes.

  3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

Test or Research Source

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

  • Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
  • Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
  • Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
  • Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
  • Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ .