Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain or compromise WordPress author-level account
-
DeliveryCraft display callback bypassing blocked-function comparison
-
ExploitSubmit callback via Pods custom field interface
-
ExecutionServer executes arbitrary PHP in web process context
-
ImpactFull server-side code execution achieved
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires three simultaneous conditions: (1) the Pods WordPress plugin must be installed and active in a version between 3.1.0 and 3.3.9.1; (2) restricted display-callback mode must be enabled - this is the automatic default only for installations whose first Pods version predated 3.1, meaning newer clean installs are NOT affected by default; (3) the attacker must hold at minimum a WordPress author-level account (PR:H per CVSS vector). Sites first installed on Pods 3.1 or later with default settings, or sites without any untrusted author-level accounts, are not exploitable. User interaction is not required (UI:N), but the need for an authenticated author account limits exploitation to insiders or attackers who have separately compromised credentials. These three conditions substantially narrow the real-world exploitable population beyond what the 7.2 CVSS score alone implies. |
| Impact | The CVSS 3.1 score of 7.2 with vector AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H captures the network exploitability and severe code-execution impact accurately, but the PR:H designation is the key limiting signal: exploitation cannot be achieved without at minimum a WordPress author-level account, which meaningfully reduces casual attack surface. EPSS at 0.21% (11th percentile) is consistent with this - the public exploit exists but practical exploitation requires account access, suppressing mass scanning utility. This CVE is not in CISA KEV, confirming no confirmed widespread in-the-wild campaigns at time of analysis. The highest real-world risk belongs to sites that: (1) have been running Pods since before version 3.1 (restricted mode is active by default), and (2) allow untrusted third parties to register as contributors or authors. Sites with tightly controlled contributor rosters face substantially lower risk. CVSS alone would overstate urgency for most deployments. |
| Exploit ScenarioDerived | An attacker with a WordPress author account on a target site running Pods 3.1.0-3.3.9.1 with restricted display-callback mode active submits a crafted display callback value that exploits the blocklist comparison flaw. The malformed callback name passes the flawed check and is executed by the server as arbitrary PHP code. A public exploit is available per WPScan intelligence, lowering the skill barrier for exploitation once account access is obtained. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 26, 2026
Remote code execution in the Pods WordPress plugin (versions 3.1.0 through 3.3.9.1) allows authenticated users holding the author role or higher to invoke arbitrary PHP functions on the server by submitting a crafted display callback that bypasses the plugin's blocked-function comparison logic. Exploitation is limited to sites where restricted display-callback mode is active - the automatic default on installations first deployed on Pods versions predating 3.1 - meaning a large subset of long-running Pods deployments are in-scope. A public exploit exists per WPScan reporting, though EPSS at 0.21% (11th percentile) indicates low observed exploitation activity and no CISA KEV listing at time of analysis.
RemediationAI
Upgrade the Pods WordPress plugin to version 3.3.9.1 or later, which corrects the flawed blocked-function comparison (vendor-released patch confirmed via WPScan advisory https://wpscan.com/vulnerability/4972f315-3819-4fb9-b56a-a88df992416e/). If immediate patching is not possible, the primary compensating control is auditing and restricting WordPress user roles: remove or demote untrusted accounts from the author role and above, since PR:H is required for exploitation - eliminating untrusted author accounts removes the attack vector entirely. As a secondary measure, administrators can review whether restricted display-callback mode can be temporarily disabled for the affected Pods installation, but note this removes the security boundary the feature provides and may expose other callback-related risks. Standard WordPress hardening (limiting user registration, enforcing strong credentials on author accounts) should accompany any mitigation.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Pods is a WordPress content type and field management plugin (CPE: cpe:2.3:a:unknown:pods:*:*:*:*:*:*:*:*). Its restricted display-callback mode is a security feature intended to limit which PHP functions can be referenced as display callbacks for custom fields. The root cause is CWE-94 (Improper Control of Generation of Code - Code Injection): the plugin's comparison routine that checks a user-supplied callback name against its internal blocklist of disallowed functions contains a logic flaw that allows the restriction to be circumvented. Because WordPress executes registered callbacks in the web server process, a successfully injected callback runs with the full privileges of the web server user, enabling arbitrary PHP code execution. The vulnerability was discovered and reported by WPScan (EUVD-2026-66277).
Know when Pods gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Network-reachable via WordPress interface but requires author-level credentials (PR:H); arbitrary PHP execution justifies full C/I/A with unchanged scope.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The Pods WordPress plugin before 3.3.9.1 does not correctly compare a display callback against its list of blocked functions, allowing users with the author role and above to execute arbitrary code on the server. Only sites using the restricted display-callback mode are affected, which is the automatic default on installations whose first Pods version predates 3.1.
Executive ViewAI
The Pods WordPress plugin (versions 3.1.0-3.3.9.1) contains a remote code execution vulnerability that allows authenticated users with author-level permissions to execute arbitrary PHP functions on affected WordPress sites. This directly threatens website integrity and data security for organizations relying on Pods, particularly those with long-running deployments using the default restricted display-callback mode. While a vendor patch is available and exploitation remains low (EPSS 0.2%), the public availability of exploit code necessitates swift remediation.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Multiple cross-site request forgery (CSRF) vulnerabilities in the Pods plugin before 2.5 for WordPress allow remote atta
Arbitrary file read in the Pods WordPress plugin before 3.3.9.2 allows users holding the Author role or higher to exfilt
The Pods - Custom Content Types and Fields WordPress plugin before 2.7.27 was vulnerable to an Authenticated Stored Cros
The Pods - Custom Content Types and Fields WordPress plugin before 2.7.27 was vulnerable to an Authenticated Stored Cros
The Pods - Custom Content Types and Fields plugin for WordPress is vulnerable to Remote Code Exxecution via shortcode in
The Pods - Custom Content Types and Fields plugin for WordPress is vulnerable to SQL Injection via shortcode in all vers
The Pods WordPress plugin before 3.2.7.1 does not sanitise and escape some of its settings, which could allow high privi
Cross-Site Request Forgery (CSRF) vulnerability in Pods Framework Team Pods - Custom Content Types and Fields plugin <=
Cross-site scripting (XSS) vulnerability in the Pods plugin before 2.5 for WordPress allows remote attackers to inject a
Unauthenticated reflected/stored cross-site scripting in the Pods WordPress plugin (versions 3.3.8 and earlier) allows r
The Pods - Custom Content Types and Fields plugin for WordPress is vulnerable to Missing Authorization in all versions u
The Pods WordPress plugin before 3.2.8.2 does not sanitize and escape a parameter before using it in a SQL statement, al
EUVD-2026-66277
GHSA-hqrq-6pwc-6v3j
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB