CVE-2025-31527
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 Kishan WP Link Preview wp-link-preview allows Server Side Request Forgery.This issue affects WP Link Preview: from n/a through <= 1.4.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 confidenceServer-Side Request Forgery (SSRF) vulnerability in the Kishan WP Link Preview WordPress plugin allows attackers to induce the server to make arbitrary HTTP requests to internal services, cloud metadata endpoints, or external targets by manipulating URL parameters processed by the plugin.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 WP Link Preview plugin is installedNavigate to WordPress admin dashboard > Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'wp-link-preview' or similar Kishan link preview pluginAffected if The plugin appears in the installed plugins list or filesystem
-
Identify the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > click the plugin name to view the version in the plugin header, or read the main plugin PHP file and look for 'Version:' in the file header commentAffected if The displayed version matches any version known to contain this SSRF vulnerability (compare against official vulnerability disclosures)
-
Confirm the link preview functionality is activeCheck if any post types, shortcodes, or widgets related to link preview are enabled in the WordPress admin settings, or verify the plugin's shortcode (commonly [kishan_link_preview] or similar) is in use on any published contentAffected if The link preview feature is enabled or the shortcode appears in live content, making the SSRF endpoint accessible
-
Inspect HTTP access logs for suspicious requestsReview Apache/nginx access logs (typically in /var/log/apache2/ or /var/log/nginx/) for incoming requests to your site that contain unusual URL parameters pointing to internal IPs (127.0.0.1, 169.254.169.254), private network ranges, or external domainsAffected if Logs show requests with manipulated URL parameters that the plugin processed, indicating active exploitation attempts
The environment is affected if the Kishan WP Link Preview plugin is installed with a vulnerable version and the link preview feature is accessible to users, enabling attackers to trigger arbitrary HTTP requests through manipulated URL parameters.
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 dataDisable or remove the WP Link Preview plugin until an official patch is released; implement WAF rules to filter SSRF attack patterns and restrict outgoing requests to trusted domains.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31527 — 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-31527 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