dbcve.org
Link LibraryWordPress extension · Ylefebvre

CVE-2025-46237

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-22
Fix available
A fix is available. Upgrade to 7.8.1 or later.
See remediation →
58/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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Yannick Lefebvre Link Library link-library allows Stored XSS.This issue affects Link Library: from n/a through <= 7.8.

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

Stored Cross-site Scripting (XSS) vulnerability in the Link Library WordPress plugin allows authenticated attackers to inject malicious JavaScript code through plugin input fields. When administrators or other users view the affected pages containing the injected script, it executes in their browsers, potentially enabling session hijacking or defacement.

MitigationUpdate Link Library plugin to the latest version when available, or implement proper input sanitization using WordPress sanitization functions (sanitize_text_field, esc_attr, esc_html) and add nonce verification on all form submissions in the plugin.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Link LibraryWordPress extension
Affected:< 7.8.1

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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Link Library plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Link Library' or check the /wp-content/plugins/link-library directory exists
    Affected if Link Library plugin is not installed - not affected
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Link Library, or inspect the plugin's main PHP file header for 'Version:' tag, or check /wp-content/plugins/link-library/readme.txt for version number
    Affected if Version is less than 7.8.1 - vulnerable to this CVE
  3. Identify plugin input fields
    Access Link Library settings pages (Links > Link Library or similar admin menu items) and examine form fields where users can enter link data such as link name, URL, description, or custom fields
    Affected if Plugin has active input fields accepting user-supplied content - potential injection point exists
  4. Inspect stored data for malicious scripts
    Check WordPress database wp_posts table for any entries with post_type related to link-library, or view the public-facing link directory pages and view page source to see if any script tags are present in link data fields
    Affected if Script tags, javascript: URIs, or onmouseover/onerror attributes appear in stored link data - indicates active exploitation

User is affected if Link Library plugin version is below 7.8.1 and the plugin is actively storing user-supplied content in its input fields that could be viewed by administrators or other users.

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
Upgrade available Upgrade to 7.8.1 or later
Fixed in 7.8.1
Interim mitigation

Update Link Library plugin to the latest version when available, or implement proper input sanitization using WordPress sanitization functions (sanitize_text_field, esc_attr, esc_html) and add nonce verification on all form submissions in the plugin.

Recommended fix High confidence

7.8.1

  1. 1. Back up your WordPress site before making any plugin updates.
  2. 2. Navigate to the WordPress admin dashboard > Plugins page.
  3. 3. Find the Link Library plugin in the list of installed plugins.
  4. 4. If an update is available, click 'Update Now' to upgrade to version 7.8.1 or later.
  5. 5. Alternatively, go to Dashboard > Updates and select Link Library to update.
  6. 6. After updating, verify the plugin is running version 7.8.1 or higher under Plugins > Installed Plugins.

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

Fix this in Link Library Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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