CVE-2025-58641
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 · uneditedServer-Side Request Forgery (SSRF) vulnerability in kamleshyadav Exit Intent Popup exitintentpopup allows Server Side Request Forgery.This issue affects Exit Intent Popup: from n/a through <= 1.0.1.
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 confidenceA Server-Side Request Forgery (SSRF) vulnerability exists in the Exit Intent Popup WordPress plugin by kamleshyadav (versions up to 1.0.1). The vulnerability allows an attacker to induce the server to make arbitrary HTTP requests to internal or external resources, potentially accessing internal services, cloud metadata endpoints, or performing reconnaissance.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Exit Intent Popup plugin is installedLog in to WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'Exit Intent Popup' or 'kamleshyadav' in the plugin listAffected if plugin is present in the WordPress installation
-
Check installed plugin versionIn the Plugins list, click on the plugin name or view details to find the version number displayed under the plugin titleAffected if version is 1.0.1 or lower (any version up to and including 1.0.1)
-
Confirm plugin is activeIn Plugins > Installed Plugins, verify the Exit Intent Popup plugin shows as 'Active' under the status columnAffected if plugin is activated (inactive plugins cannot be exploited)
-
Identify plugin entry pointLocate the plugin files via FTP or file manager at wp-content/plugins/exit-intent-popup/ and note any PHP files that handle HTTP requests (look for functions like wp_remote_get, file_get_contents with URLs, or cURL calls)Affected if plugin files contain code that fetches external URLs based on user input
User is affected if the Exit Intent Popup plugin by kamleshyadav is installed, active, and running version 1.0.1 or lower, with an entry point that allows attacker-controlled URL input to trigger SSRF.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to the latest version of the Exit Intent Popup plugin when available, or disable the plugin until a patch is released. If immediate remediation is required, implement URL validation and restrict outbound requests to allowlisted domains only.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58641 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-58641 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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