Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify Pods <= 3.3.8 target
-
DeliveryCraft malicious XSS payload URL
-
ExploitPhish WordPress admin victim
-
ExecutionVictim browser loads payload
-
PersistScript executes in WP origin
-
ImpactHijack session or create rogue admin
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires (1) the target WordPress site to have the Pods plugin installed at version 3.3.8 or earlier, (2) the vulnerable Pods endpoint to be reachable by the unauthenticated attacker over the network (PR:N, AV:N), and (3) a victim - typically an authenticated WordPress user or administrator - to interact with attacker-controlled content such as a malicious link or page (UI:R). Limiting factors: the required user interaction means drive-by mass exploitation is not possible without successful social engineering, and the C:L/I:L/A:L impact metrics indicate the immediate damage is bounded to what script in the victim's browser session can achieve rather than direct server compromise. |
| Impact | CVSS 3.1 base score of 7.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L) reflects a network-reachable, low-complexity, unauthenticated bug whose impact depends on a victim clicking a crafted link or visiting an attacker-controlled page (UI:R). The scope-change flag elevates the practical severity because injected script can act against the WordPress admin or another security context (e.g., session hijack of a logged-in administrator). EPSS and CISA KEV status are not provided in the input - neither active exploitation nor exploitation probability can be confirmed from available data. No POC was identified; the Patchstack reference is a vulnerability database listing rather than published exploit code, so this currently looks like a credible but not-yet-weaponized XSS in a widely deployed plugin. |
| Exploit ScenarioDerived | An attacker crafts a URL or web page containing a malicious payload that triggers the unsanitized Pods endpoint, then phishes a WordPress administrator into clicking it via email, social media, or a comment link. When the admin's browser renders the response, the injected JavaScript runs in the WordPress origin and can exfiltrate session cookies, create a rogue admin account via the REST API, or pivot to full site takeover. No public exploit identified at time of analysis, but XSS proof-of-concepts for similar Patchstack-disclosed WordPress plugins are typically trivial to reconstruct from the advisory. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 16, 2026
Unauthenticated reflected/stored cross-site scripting in the Pods WordPress plugin (versions 3.3.8 and earlier) allows remote attackers to inject malicious script that executes in a victim's browser when they visit a crafted page or link. The flaw requires user interaction (UI:R) and carries a scope change (S:C), letting injected payloads steal session data or perform privileged actions in the WordPress admin context. No public exploit identified at time of analysis, but the unauthenticated nature and broad WordPress plugin install base make this a meaningful risk for site operators.
RemediationAI
Upgrade the Pods plugin to a version newer than 3.3.8 once a fixed release is published by the maintainers - patch status in the supplied data is unclear, so this should be characterized as 'Upstream fix availability not independently confirmed; consult the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/pods/vulnerability/wordpress-pods-plugin-3-3-8-cross-site-scripting-xss-vulnerability for the current fixed version.' In the interim, deploy a WAF rule (Patchstack, Wordfence, or equivalent) to filter XSS payloads targeting Pods endpoints, restrict access to the affected plugin pages via IP allow-listing where feasible (side effect: blocks legitimate remote contributors), enforce strict Content Security Policy headers on the WordPress site to reduce script execution impact (side effect: may break inline scripts in themes), and require administrators to log out of WordPress before browsing untrusted links.
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 popular WordPress content-development framework (cpe:2.3:a:pods_framework:pods) used to create and extend custom content types, fields, and taxonomies. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation), meaning user-controllable input is reflected or stored without proper output encoding or input sanitization. Because the vector is network-reachable and requires no authentication, the unsanitized sink is exposed on a public-facing endpoint of the plugin, allowing attacker-supplied script to be rendered in a victim's browser session against the WordPress origin.
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:N/UI:R/S:C/C:L/I:L/A:L
Network-reachable unauthenticated XSS (PR:N, AV:N, AC:L) requiring victim click (UI:R); injected script crosses into the WordPress admin context (S:C) with limited C/I/A impact.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Cross Site Scripting (XSS) in Pods <= 3.3.8 versions.
Executive ViewAI
The Pods WordPress plugin (versions 3.3.8 and earlier) contains an unauthenticated cross-site scripting vulnerability that allows remote attackers to inject arbitrary scripts into affected WordPress sites. Successful exploitation could enable session hijacking, admin account compromise, and unauthorized administrative actions. Organizations using this plugin must immediately assess exposure and implement interim security controls pending vendor patching.
No vendor-released patch identified at time of analysis. Implement Web Application Firewall rules to detect and block XSS injection attempts; enforce strict Content Security Policy headers to restrict script execution; restrict WordPress admin panel access by IP allowlist; enable multi-factor authentication on all administrative accounts; configure session monitoring and anomaly detection for admin user activity; establish monthly plugin file integrity verification process. Apply vendor patch immediately upon release.
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
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Remote code execution in the Pods WordPress plugin (versions 3.1.0 through 3.3.9.1) allows authenticated users holding t
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
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-37053
GHSA-c45f-2556-9gh3
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB