CVE-2025-1446: The Pods WordPress plugin before 3.2.8.2 does not sanitize and escape a parameter before using it in a SQL st

Q: How do I fix CVE-2025-1446?

pods: upgrade to 3.2.8.2. Exact commands for each OS are on this page.

Q: Is CVE-2025-1446 being exploited?

CVE-2025-1446 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-1446 affect?

CVE-2025-1446 affects pods. Severity is critical (CVSS 9.8). The Pods WordPress plugin before 3.2.8.2 does not sanitize and escape a parameter before using it in a SQL statement, allowing admins to perform SQL injection attacks

Q: How urgent is CVE-2025-1446?

Priority 53/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2025-1446 is a critical-severity flaw (CVSS 9.8) affecting pods. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Pods WordPress plugin before 3.2.8.2 does not sanitize and escape a parameter before using it in a SQL statement, allowing admins to perform SQL injection attacks

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 64%)
CISA exploited list	No
Weakness	CWE-89
Published	2025-03-23
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: podsfoundation

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-03-23 06:15 UTCPublished CVE record published
2026-06-17 08:39 UTCUpdated Record last modified

podsfoundation pods UPGRADE

Affected: < 3.2.8.2

Fixed in: 3.2.8.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy pods || rpm -q pods || pods --version

2. UPGRADE to 3.2.8.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade pods

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade pods

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-1446?

pods: upgrade to 3.2.8.2. Exact commands for each OS are on this page.

Is CVE-2025-1446 being exploited?

CVE-2025-1446 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-1446 affect?

CVE-2025-1446 affects pods. Severity is critical (CVSS 9.8). The Pods WordPress plugin before 3.2.8.2 does not sanitize and escape a parameter before using it in a SQL statement, allowing admins to perform SQL injection attacks

How urgent is CVE-2025-1446?

Priority 53/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-9883 MEDIUM 4.8 UPGRADE The Pods WordPress plugin before 3.2.7.1 does not sanitise and escape some of its settings, which could allow
CVE-2024-11849 MEDIUM 6.1 UPGRADE The Pods WordPress plugin before 3.2.8.1 does not sanitise and escape some of its settings, which could allow

References

← Back to latest CVEs