dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-31824

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Server-Side Request Forgery (SSRF) vulnerability in Wombat Plugins WP Optin Wheel wp-optin-wheel allows Server Side Request Forgery.This issue affects WP Optin Wheel: from n/a through <= 1.4.7.

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

Server-Side Request Forgery (SSRF) vulnerability in the WP Optin Wheel WordPress plugin (versions <= 1.4.7) allows remote attackers to make the server perform unintended requests to internal or external resources. The vulnerability stems from insufficient validation of user-supplied URLs or endpoints within the plugin's functionality.

MitigationUpdate WP Optin Wheel to the latest available version that patches this vulnerability, or if no update exists, remove the plugin until a fix is available. Implement network segmentation to limit the impact of potential SSRF attacks.

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

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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Verify WP Optin Wheel plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'wp-optin-wheel' or similar
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Check installed plugin version
    In WordPress admin > Plugins, find WP Optin Wheel and view the version number displayed under the plugin name, or open the main plugin PHP file and look for the 'Version' header in the plugin comments
    Affected if The displayed version number is 1.4.7 or lower
  3. Confirm plugin is active
    In WordPress admin > Plugins, check if WP Optin Wheel shows as 'Active' rather than 'Inactive' or 'Must-Use'
    Affected if The plugin status is Active and the version is 1.4.7 or lower
  4. Identify any wheel configurations using external URLs
    Access the plugin settings or wheel creation interface in WordPress admin. Look for any fields that accept URLs such as webhook URLs, callback endpoints, redirect URLs, or integration URLs. Check the wp_postmeta database table for any postmeta entries related to the plugin that contain http:// or https:// URLs
    Affected if Any wheel, campaign, or optin configuration contains user-supplied or configurable external URLs and the plugin version is 1.4.7 or lower

You are affected if WP Optin Wheel plugin version 1.4.7 or lower is installed and active, with any configured functionality that accepts or processes external URLs.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WP Optin Wheel to the latest available version that patches this vulnerability, or if no update exists, remove the plugin until a fix is available. Implement network segmentation to limit the impact of potential SSRF attacks.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-31824 — 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-2025-31824 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