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.
CVE-2026-74851
Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-08-26. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.2; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.2
- EG Score
- 7.2(high)
- EG Risk
- 33(Track)EG Risk 33/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity72% × 45%Exploitation1% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 41%
- KEV
- Not listed
Published
August 26, 2026
Last Modified
August 26, 2026
Advisory Details (1)
Auto-updated Aug 26, 2026Pods < 3.3.9.1 – Author+ RCE via Shortcode Display Callback | CVE 2026-74851 | Plugin Vulnerabilities
https://wpscan.com/vulnerability/4972f315-3819-4fb9-b56a-a88df992416e/Vendor Advisories for CVE-2026-74851(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 17× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 18:52 UTCGHSA enrichment
- 2026-08-29 06:44 UTCEG score recompute
- 2026-08-29 06:44 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 18:36 UTCGHSA enrichment
- 2026-08-28 06:20 UTCGHSA enrichment
- 2026-08-27 18:07 UTCEG score recompute
- 2026-08-27 18:07 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 04:48 UTCEG score recompute
- 2026-08-27 04:48 UTCGHSA enrichment
- 2026-08-26 15:03 UTCEG score recompute▲ 7.20
- 2026-08-26 15:01 UTCMITRE cvelistV5CVSS v3 → 7.2 · severity → HIGH
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 06:10 UTCEG score recompute
- 2026-08-26 06:08 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-94
- CVE-2003-1432EG 10.0EPSS p94HIGH
- CVE-2002-0495EG 10.0EPSS p96HIGH
- CVE-1999-0702EG 10.0EPSS p98HIGH
- CVE-1999-0509EG 10.0EPSS p98HIGH
- CVE-2006-1318EG 9.3EPSS p97HIGH
- CVE-2006-1301EG 9.3EPSS p95HIGH
- CVE-2006-1308EG 9.3EPSS p95HIGH
- CVE-2006-1309EG 9.3EPSS p95HIGH
- CVE-2006-1304EG 9.3EPSS p96HIGH
- CVE-2006-1306EG 9.3EPSS p95HIGH
Frequently asked(5)
What is CVE-2026-74851?
When was CVE-2026-74851 disclosed?
Is CVE-2026-74851 actively exploited?
What is the CVSS score of CVE-2026-74851?
How do I remediate CVE-2026-74851?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-74851
Is Your Infrastructure Affected by CVE-2026-74851?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.