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

CVE-2025-39547

HIGH · 7.1 CVSS v3.1 Published 2025-04-16
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 Toast Plugins Internal Link Optimiser internal-link-finder allows Stored XSS.This issue affects Internal Link Optimiser: from n/a through <= 5.1.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

CSRF vulnerability in the Internal Link Optimiser plugin allows authenticated attackers to inject malicious scripts via stored XSS. The plugin lacks proper CSRF protection, enabling attackers to trick administrators into executing requests that store malicious JavaScript in the internal link finder functionality.

MitigationImplement CSRF tokens on all forms and AJAX actions, and apply proper input validation and output encoding to prevent stored XSS in the internal link fields.

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 Internal Link Optimiser plugin is installed
    Check the WordPress plugin directory for the Internal Link Optimiser plugin files. In a WordPress environment, inspect wp-content/plugins/ for a folder named 'internal-link-optimiser' or similar.
    Affected if The plugin folder exists and the plugin is active in the WordPress installation
  2. Identify the installed plugin version
    Open the main plugin PHP file and locate the version header comment (e.g., 'Version: x.x.x') or check the plugin metadata via WordPress admin under Plugins > Installed Plugins.
    Affected if The version number returned falls within any known vulnerable version range for this CVE
  3. Confirm the internal link finder functionality is present
    Access the plugin settings page in WordPress admin and locate the Internal Link Optimiser or Link Finder feature. Check if the functionality to add or manage internal links is accessible.
    Affected if The internal link finder feature is present and accessible in the admin dashboard
  4. Inspect forms for CSRF protection
    View the page source of the plugin admin pages. Look for a nonce field or CSRF token in all forms and AJAX requests related to the internal link functionality. Common nonce field names include '_wpnonce', 'security', or 'csrf_token'.
    Affected if Forms and AJAX actions lack a CSRF nonce token or token validation is missing
  5. Check stored link data for malicious scripts
    Review any stored internal link entries in the database (typically in wp_options or a custom table created by the plugin). Inspect the stored URL and anchor text fields for unsanitized script tags or JavaScript event handlers.
    Affected if Stored link data contains unescaped HTML, script tags, or JavaScript event attributes that could execute

The environment is affected if the Internal Link Optimiser plugin is active with a vulnerable version and the internal link finder functionality lacks CSRF token protection, allowing stored XSS payloads to be persisted.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement CSRF tokens on all forms and AJAX actions, and apply proper input validation and output encoding to prevent stored XSS in the internal link fields.

Recommended fix Moderate confidence

Latest version of Internal Link Optimiser (version > 5.1.3)

  1. 1. Log into the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Internal Link Optimiser' (internal-link-finder) by Toast Plugins
  4. 4. Check if an update is available for this plugin
  5. 5. If an update is available, update to the latest version to resolve the CSRF vulnerability
  6. 6. If no update is available through the WordPress admin, visit the official WordPress plugin repository or Toast Plugins website to download the latest version
  7. 7. After updating, verify the plugin is functioning correctly and test that the CSRF protection is working
Caveat Review plugin settings after upgrade as configuration may need adjustment

Generated from the published advisory — verify against the referenced sources before acting.

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