dbcve.org
PodsWordPress extension · Podsfoundation

CVE-2023-23790

HIGH · 8.8 CVSS v3.1 Published 2023-05-03
Fix available
A fix is available. Upgrade to 2.9.11 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-Site Request Forgery (CSRF) vulnerability in Pods Framework Team Pods – Custom Content Types and Fields plugin <= 2.9.10.2 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Pods Framework WordPress plugin allows attackers to induce authenticated users to perform unintended actions by tricking them into submitting malicious requests.

MitigationUpgrade to a version newer than 2.9.10.2; implement anti-CSRF tokens (nonces) on all state-changing operations and ensure proper referer validation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PodsWordPress extension
Affected:< 2.9.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Pods plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Pods Framework' or 'Pods - Custom Content Types and Fields'. Alternatively, check the /wp-content/plugins/ directory for a pods folder.
    Affected if The Pods plugin folder exists in the WordPress installation
  2. Check installed Pods version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number listed under the Pods plugin description. Alternatively, check the main plugin file header in /wp-content/plugins/pods/readme.txt or /wp-content/plugins/pods/pods.php for the Version: field.
    Affected if The version is lower than 2.9.11 (for example: 2.9.10, 2.9.9, etc.)
  3. Identify state-changing operations
    Review Pods plugin settings pages where users can create, edit, or delete content types, fields, or pods. Common areas include: Pods admin menu items, any form submissions within the Pods settings, or AJAX actions triggered by the plugin.
    Affected if State-changing forms or actions exist in the Pods plugin without anti-CSRF nonce verification
  4. Verify nonce protection on Pods forms
    Inspect the HTML source of Pods admin forms (create/edit content types, field management, etc.) to check if they contain a hidden nonce field (typically named _wpnonce or _wp_nonce) or if the form submits to an endpoint that validates nonces.
    Affected if Forms lack nonce fields or the submissions do not validate tokens

Your environment is affected if the Pods plugin is installed with a version lower than 2.9.11 and any state-changing operations within Pods lack anti-CSRF token protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.9.11 or later
Fixed in 2.9.11
Interim mitigation

Upgrade to a version newer than 2.9.10.2; implement anti-CSRF tokens (nonces) on all state-changing operations and ensure proper referer validation.

Recommended fix High confidence

2.9.11 or later

  1. Backup your WordPress site database and files before proceeding with any updates
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Locate the 'Pods – Custom Content Types and Fields' plugin
  4. Click 'Update now' when version 2.9.11 or later is available, or manually upload the latest version from the WordPress plugin repository
  5. Verify the plugin updated successfully by checking the installed version number
  6. Test that your custom content types and fields are functioning correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pods Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-23790 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-23790 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data