Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-19598 – Unauthenticated Privilege Escalation to Administrator – Pods (Custom Content Types

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-19598 is a critical authorization bypass vulnerability in the Pods – Custom Content Types and Fields WordPress plugin, allowing unauthenticated attackers to escalate privileges to Administrator. The flaw carries a CVSS v3.1 base score of 9.8 (Critical) and affects all releases up to and including 3.3.9. Successful exploitation can lead to full site takeover, including resetting the password of any user account, such as the site owner.

Technical details

  • Root cause: The pods_admin AJAX router routes every access check — method allowlist, nonce verification, login enforcement, and capability gate — through the pods_error() function.
  • Trigger conditions: Under the JSON meta-box-loader compatibility code path, pods_error() only writes the failure to the PHP error log and returns false instead of terminating the request, so the authorization checks are effectively bypassed.
  • Attack vector: Network-based; no authentication or user interaction is required to reach and abuse the vulnerable AJAX endpoint.
  • Impact: Unauthenticated attackers can escalate to Administrator privileges, overwrite any user’s password (including the site owner), or perform other privileged administrative actions, resulting in complete compromise of the WordPress site.
  • Weakness classification: CWE-863 (Incorrect Authorization).

Affected software

  • Pods – Custom Content Types and Fields, versions 2.8 through 2.8.23.3
  • Version 2.9 through 2.9.19.3
  • Version 3.0 through 3.0.10.3
  • Version 3.1 through 3.1.4.1
  • Version 3.2 through 3.2.8.2
  • Version 3.3 through 3.3.9

Severity

CVSS v3.1 Base Score: 9.8 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Update the Pods plugin to the first version released after 3.3.9 that addresses this authorization bypass. Confirm the exact patched build via the official WordPress.org plugin changelog before deploying, as a specific fixed version number was not consistently published across sources at the time of writing.
  • If no patch is available: Restrict or disable access to the pods_admin AJAX endpoint (e.g., via web application firewall rules blocking unauthenticated requests to admin-ajax.php with the relevant Pods action parameters) until an update can be applied, and monitor server/PHP error logs for repeated authorization-check failures tied to Pods, which may indicate exploitation attempts.
  • Review WordPress user accounts (especially Administrator roles) for unauthorized changes or password resets following any suspected exploitation.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: /wp-content/plugins/pods/

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge