dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-39415

HIGH · 7.1 CVSS v3.1 Published 2025-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 Jayesh Parejiya Social Media Links social-media-links allows Stored XSS.This issue affects Social Media Links: from n/a through <= 1.0.3.

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

A CSRF vulnerability in the Social Media Links WordPress plugin (versions up to 1.0.3) allows authenticated administrators to be tricked into storing malicious JavaScript payloads via forged requests. Since the XSS is stored, it executes whenever users view the affected social media links, enabling session hijacking and credential theft.

MitigationApply vendor patch when available; in the interim, disable the plugin or restrict admin access to trusted users only. Implement WordPress nonce verification on all form submissions and ensure proper output escaping for stored data.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 the Social Media Links plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Social Media Links'. The version number is displayed below the plugin name. Compare it to the affected range: versions 1.0.3 and below.
    Affected if The installed version is 1.0.3 or any earlier version.
  2. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and check if 'Social Media Links' shows as 'Active'. The vulnerability only applies when the plugin is active.
    Affected if The plugin is active and the version is 1.0.3 or below.
  3. Inspect stored social media link URLs for malicious scripts
    Navigate to the plugin settings page where social media links are configured (typically under Settings > Social Media Links or a dedicated menu item). Examine each URL field for suspicious characters such as 'javascript:', event handlers like 'onload', 'onerror', or script tags.
    Affected if Any stored URL contains 'javascript:' protocol, script tags, or HTML event attributes.
  4. Review the plugin settings in the WordPress database
    Access the WordPress database via phpMyAdmin or command line. Look for entries in the wp_options table (or relevant options table with prefix) where option_name contains 'social_media_links' or similar. Inspect option_value for encoded scripts, unusual HTML, or XSS payloads.
    Affected if The database contains option values with script tags, event handlers, or encoded JavaScript payloads.
  5. Check recent admin activity for forged requests
    Review WordPress activity logs, server access logs, or security plugins for suspicious POST requests to the plugin admin pages, especially from admin user sessions that may have been coerced.
    Affected if There are anomalous POST requests to plugin endpoints originating from admin users, especially if nonce verification is missing.

A user is affected if the Social Media Links plugin version 1.0.3 or below is installed and active, with any stored social media link containing JavaScript payloads or XSS-enabling content.

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

Apply vendor patch when available; in the interim, disable the plugin or restrict admin access to trusted users only. Implement WordPress nonce verification on all form submissions and ensure proper output escaping for stored data.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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