dbcve.org
Link LibraryWordPress extension · Ylefebvre

CVE-2024-35687

MEDIUM · 6.1 CVSS v3.1 Published 2024-06-08
Fix available
A fix is available. Upgrade to 7.6.4 or later.
See remediation →
68/100
Remediation priority · Elevated
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
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Yannick Lefebvre Link Library link-library allows Reflected XSS.This issue affects Link Library: from n/a through 7.6.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 · moderate confidence

A reflected XSS vulnerability exists in the Link Library WordPress plugin (versions through 7.6.3) where unsanitized user input is improperly neutralized during web page generation, allowing attackers to inject malicious scripts that execute in the context of a user's browser session.

MitigationUpdate Link Library to the latest patched version when released; until then, implement output escaping on all user-supplied parameters and validate/sanitize input at entry points.

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.6.4

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
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Check Link Library plugin version
    Navigate to WordPress Admin > Plugins > Installed Plugins and locate 'Link Library' in the list. The version number is displayed below the plugin name. Alternatively, inspect the plugin main file (link-library.php) and look for the 'Version' comment header or the $plugin_version variable.
    Affected if The displayed version number is less than 7.6.4 (for example, 7.6.3, 7.6.2, etc.)
  2. Confirm plugin is active
    In WordPress Admin > Plugins, verify that the Link Library plugin has an 'Active' status under the plugin name.
    Affected if The plugin is active and the version is below 7.6.4
  3. Identify exposed user input points
    Review the plugin settings pages where user-supplied data (such as search parameters, filter options, or custom link fields) are entered and reflected back in the page output. Check URLs for query parameters that the plugin processes.
    Affected if The plugin processes and reflects any user-supplied GET or POST parameters in its output without visible sanitization
  4. Inspect page source for unsanitized output
    Visit a Link Library frontend page, view the page source (right-click > View Page Source), and search for any user-supplied values that appear unescaped in HTML context (for example, unquoted attributes, inside script tags, or between HTML tags without HTML entity encoding).
    Affected if User input appears in the rendered HTML without proper escaping (for example, <script> tags execute or unescaped quotes break attribute contexts)

Your environment is affected if the Link Library plugin is active and the installed version is any version before 7.6.4, as the reflected XSS vulnerability exists in all versions through 7.6.3.

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.6.4 or later
Fixed in 7.6.4
Interim mitigation

Update Link Library to the latest patched version when released; until then, implement output escaping on all user-supplied parameters and validate/sanitize input at entry points.

Recommended fix High confidence

7.6.4

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Link Library plugin
  4. Check if the current version is below 7.6.4
  5. If an update is available, click 'Update Now' to upgrade to version 7.6.4 or later
  6. Alternatively, navigate to Dashboard > Updates and apply available updates
  7. Verify the plugin has been updated to version 7.6.4 or higher after completion

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

Fix this in Link Library 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 the upgrade done

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-2024-35687 — 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-2024-35687 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