# CVE-2026-74851: Pods < 3.3.9.1 - Author+ RCE via Shortcode Display Callback

> Authors can execute arbitrary code on the server via shortcode display callbacks in the Pods WordPress plugin when restricted mode is active.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-hqrq-6pwc-6v3j

## What is CVE-2026-74851?

CVE-2026-74851 is a high-severity code injection vulnerability in Unknown Pods, published on 26 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-74851?


## How do I fix CVE-2026-74851?

No fix has been published for CVE-2026-74851 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-74851 being exploited?

There is no known exploitation of CVE-2026-74851 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74851 and fix it if it is affected.

What it is: CVE-2026-74851 is a high-severity code injection vulnerability in Unknown Pods, published on 26 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74851 in the wild and no public exploit code.

Affected product: Unknown Pods. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-74851/ (Markdown: https://insights.sbomify.com/CVE-2026-74851/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-74851
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-74851
- OSV: https://osv.dev/vulnerability/CVE-2026-74851

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-74851/
Summaries are generated and may contain mistakes; the official description above is the record.