sales@hackhalt.com

Home / Threats / CVE-2026-74853

Pods - Security Vulnerability (CVE-2026-74853)

CVE-2026-74853

The Pods WordPress plugin before 3.3.9.2 does not restrict which functions a display callback may resolve to, allowing users with the author role and above to read arbitrary files from the server, including files outside the web root. 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-74853

MEDIUM CVSS 6.8 Published 2026-09-04 Updated 2026-09-04
AI Risk Elevated (58/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P3 Priority
Severity Band MEDIUM
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
Affected Components 1
Reference Links 1
AI Risk Engine Elevated (58/100)
Exploitability Medium
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-09-04 CVE published and first recorded in the threat feed.
  2. 2026-09-04 Record updated with latest vulnerability metadata.
  3. 2026-09-04 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 10 hours ago

AI enriched 10 hours ago (2026-09-04 18:09 UTC)

Technical Summary

The Pods WordPress plugin before 3.3.9.2 does not restrict which functions a display callback may resolve to, allowing users with the author role and above to read arbitrary files from the server, including files outside the web root. Only sites using the restricted display-callback mode are affected, which is the automatic default on installations whose first Pods version predates 3.1.

Potential Impact

Severity is MEDIUM (CVSS 6.8). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Medium based on severity and technical exposure profile.

Primary risk drivers: severity and technical exposure profile

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 58/100 (Elevated, Medium) with priority P3 Priority. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Pods PLUGIN · pods Affected: < 3.3.9.2 Fixed in: 3.3.9.2

References

What to do about this

Patch on your next cycle Worth fixing, but not ahead of other work.

Fix it

Update Pods to 3.3.9.2 or later.

That is the complete fix. Everything below is what protects you in the meantime.

No Hack Halt control meaningfully contains this one — updating is the remedy. We would rather say so than sell you something that will not help.

Start free

Not sure if you are affected?

Scan your site to see whether it runs Pods, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs Pods. Versions below 3.3.9.2 are vulnerable; that release and later are not. An attacker needs author or above, so open registration materially increases the risk.

How do I fix it?

Update Pods to version 3.3.9.2 or later. That is the complete fix.