Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2023-6965: The Pods – Custom Content Types and Fields plugin for WordPress is vulnerable to Missing Authorization in all

27
Routine
MEDIUM 4.3UPGRADE

CVE-2023-6965 is a medium-severity flaw (CVSS 4.3) affecting pods. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Pods – Custom Content Types and Fields plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 3.0.10 (with the exception of 2.7.31.2, 2.8.23.2, 2.9.19.2). This is due to the fact that the plugin allows the use of a file inclusion feature via shortcode. This makes it possible for authenticated attackers, with contributor access or higher, to create pods and users (with default role).

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score4.3 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.6% (top 54%)
CISA exploited listNo
WeaknessCWE-862
Published2024-04-09
Last modified2026-06-17
Publisher (CNA): Wordfence · Vendor: podsfoundation

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

podsfoundation pods UPGRADE
Affected: < 2.7.31.2 · >= 2.8 and < 2.8.23.2 · >= 2.9 and < 2.9.19.2 · >= 3.0.0 and < 3.0.10.2
Fixed in: 2.7.31.2, 2.8.23.2, 2.9.19.2, 3.0.10.2
Safe to downgrade to: a release before 2.8
1. Check installed version
apt-cache policy pods || rpm -q pods || pods --version
2. UPGRADE to 2.7.31.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.
3. If no update is available yet, DOWNGRADE to a release before 2.8 (Debian / Ubuntu)
apt-cache madison pods sudo apt install pods=<VERSION_BEFORE_2.8> sudo apt-mark hold pods
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list pods sudo dnf downgrade pods-<VERSION_BEFORE_2.8> sudo dnf versionlock add pods
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
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-2023-6965?

pods: upgrade to 2.7.31.2, 2.8.23.2, 2.9.19.2, 3.0.10.2. Exact commands for each OS are on this page.

Is CVE-2023-6965 being exploited?

CVE-2023-6965 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-2023-6965 affect?

CVE-2023-6965 affects pods. Severity is medium (CVSS 4.3). The Pods – Custom Content Types and Fields plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 3.0.10 (with the exception of 2.7.31.2, 2.8.23.2, 2.9.19.2). This is due to the fact that the plugi

How urgent is CVE-2023-6965?

Priority 27/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.