CVE-2024-11849: The Pods WordPress plugin before 3.2.8.1 does not sanitise and escape some of its settings, which could allow

Q: How do I fix CVE-2024-11849?

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

Q: Is CVE-2024-11849 being exploited?

CVE-2024-11849 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-2024-11849 affect?

CVE-2024-11849 affects pods. Severity is medium (CVSS 6.1). The Pods WordPress plugin before 3.2.8.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is dis

Q: How urgent is CVE-2024-11849?

Priority 33/100. Public exploit reference

Routine

MEDIUM 6.1UPGRADE

CVE-2024-11849 is a medium-severity flaw (CVSS 6.1) 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.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 74%)
CISA exploited list	No
Weakness	CWE-79
Published	2025-01-06
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-01-06 06:15 UTCPublished CVE record published
2026-06-17 06:58 UTCUpdated Record last modified

podsfoundation pods UPGRADE

Affected: < 3.2.8.1

Fixed in: 3.2.8.1

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.1 (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-2024-11849?

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

Is CVE-2024-11849 being exploited?

CVE-2024-11849 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-2024-11849 affect?

CVE-2024-11849 affects pods. Severity is medium (CVSS 6.1). The Pods WordPress plugin before 3.2.8.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is dis

How urgent is CVE-2024-11849?

Priority 33/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2025-1446 CRITICAL 9.8 UPGRADE The Pods WordPress plugin before 3.2.8.2 does not sanitize and escape a parameter before using it in a SQL st
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

References

← Back to latest CVEs