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

CVE-2025-10861

HIGH · 7.5 CVSS v3.1 Published 2025-10-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
The Popup builder with Gamification, Multi-Step Popups, Page-Level Targeting, and WooCommerce Triggers plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.1.4. This is due to insufficient validation on the URLs supplied via the URL parameter. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services, as well as conduct network reconnaissance. The vulnerability was partially patched in version 2.1.4.

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 · high confidence

The Popup builder with Gamification plugin for WordPress is vulnerable to Server-Side Request Forgery (SSRF) in versions up to 2.1.4. The plugin fails to properly validate URLs supplied via a URL parameter, allowing unauthenticated attackers to induce the server to make arbitrary HTTP requests to internal or external resources. This can be exploited to access cloud metadata services, internal network resources, and conduct reconnaissance.

MitigationUpdate the plugin to the latest available version immediately, as version 2.1.4 contains a partial patch. Consider implementing network-level controls to restrict outbound HTTP requests from the WordPress server.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Confirm the plugin is installed
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins. Look for 'Popup builder with Gamification' in the list. Alternatively, check the plugins directory on the server at /wp-content/plugins/ for a folder named similarly to 'popup-builder-gamification' or containing 'popup' and 'gamification'.
    Affected if the plugin folder exists in the WordPress plugins directory
  2. Check the installed plugin version
    In WordPress admin, click on the plugin name to view its details, noting the version number displayed. Or open the main plugin PHP file (usually named index.php or popup-builder-gamification.php) in the plugin folder and look for a version definition in the file header comments.
    Affected if the displayed version is 2.1.4 or lower
  3. Verify the plugin is active
    In WordPress admin > Plugins > Installed Plugins, confirm the 'Popup builder with Gamification' plugin shows as 'Active'. If it is deactivated, the vulnerable code is not running.
    Affected if the plugin is currently activated on the site
  4. Identify if the vulnerable URL parameter is reachable
    Review the plugin code for HTTP request handling functions (such as wp_remote_get, wp_remote_post, file_get_contents with URLs, or cURL calls) that process a 'url' parameter. Search the plugin PHP files for strings like 'url', 'request', or 'remote'. The SSRF flaw exists where user-supplied URLs are not validated before being used in server-side requests.
    Affected if the plugin code contains functionality that accepts a URL parameter without proper validation and the site does not have additional access controls blocking unauthenticated access to that endpoint

You are affected if the Popup builder with Gamification plugin is installed, active, and running version 2.1.4 or lower, with the vulnerable URL-handling feature exposed to unauthenticated users.

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 the plugin to the latest available version immediately, as version 2.1.4 contains a partial patch. Consider implementing network-level controls to restrict outbound HTTP requests from the WordPress server.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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