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

CVE-2025-25137

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

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 kareemsultan Social Links social-links allows Cross Site Request Forgery. This issue affects Social Links: from n/a through 1.0.11.

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

Cross-Site Request Forgery (CSRF) vulnerability in the kareemsultan Social Links plugin allows attackers to trick authenticated users into submitting malicious requests that result in Stored XSS. The lack of CSRF protection on sensitive plugin functions enables attackers to inject persistent malicious scripts through social link inputs that execute when other users view the affected content.

MitigationUpdate the Social Links plugin to the latest version beyond 1.0.11 which should include CSRF token validation and proper input sanitization. If no update is available, disable the plugin until a fix is released.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Locate the Social Links plugin installation
    In WordPress, go to Plugins > Installed Plugins and look for 'Social Links' by 'kareemsultan'. Alternatively, check the wp-content/plugins directory for a folder named 'social-links' or similar.
    Affected if The Social Links plugin by kareemsultan is present in the WordPress installation
  2. Identify the installed plugin version
    In the WordPress admin Plugins page, click on the plugin name to view details, or read the 'readme.txt' or 'social-links.php' file in the plugin folder to find the Version header.
    Affected if The version is 1.0.11 or lower (or if no version is displayed and the plugin has not been updated recently)
  3. Confirm the plugin is active
    In WordPress admin, check that the Social Links plugin shows as 'Active' under the Plugin status column.
    Affected if The plugin is activated and its social link input forms are accessible to authenticated users
  4. Verify CSRF protection is absent in form handling
    Examine the main plugin PHP file (usually social-links.php) for form submissions involving social link inputs. Search for 'nonce', '_wpnonce', or 'wp_verify_nonce' around the functions that save social link settings. If these are missing, the plugin lacks CSRF protection.
    Affected if Form handling functions that save social link data do not implement nonce verification or CSRF tokens
  5. Check for input sanitization in save functions
    In the plugin PHP file, locate the functions that process and save social link input values. Look for sanitization functions like 'sanitize_text_field', 'esc_attr', or 'htmlspecialchars' applied to the social link inputs. If absent or insufficient, stored XSS is possible.
    Affected if Social link input values are saved without proper sanitization, allowing script injection

A user is affected if the Social Links plugin by kareemsultan is installed with version 1.0.11 or lower, is active, and the plugin code lacks CSRF nonce verification and proper input sanitization on social link save functions.

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 Social Links plugin to the latest version beyond 1.0.11 which should include CSRF token validation and proper input sanitization. If no update is available, disable the plugin until a fix is released.

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-25137 — 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-25137 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