dbcve.org
Link LibraryWordPress extension · Ylefebvre

CVE-2024-24875

HIGH · 8.8 CVSS v3.1 Published 2024-02-12
Fix available
A fix is available. Upgrade to after 7.5.13 or later.
See remediation →
95/100
Remediation priority · Urgent
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 Yannick Lefebvre Link Library.This issue affects Link Library: from n/a through 7.5.13.

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 Link Library WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions, such as modifying links or plugin settings, by crafting malicious requests that the victim's browser automatically sends due to lack of proper token validation.

MitigationUpgrade to Link Library version 7.5.14 or later which includes proper anti-CSRF nonce validation for state-changing operations.

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

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Link Library' by Ylefebvre in the list
    Affected if Link Library plugin is present and active in the WordPress installation
  2. Check installed version number
    On the Plugins page, find Link Library and note the version number displayed below the plugin name
    Affected if Version is 7.5.13 or lower (any version up to and including 7.5.13)
  3. Confirm admin access exists
    Determine if any administrator-level user accounts exist on this WordPress site
    Affected if Administrator accounts exist - CSRF attacks target authenticated admins
  4. Identify vulnerable plugin files
    In wp-content/plugins/link-library, inspect PHP files handling form submissions (settings, link management) for missing wp_verify_nonce or check_admin_referer calls before processing state-changing requests
    Affected if Form handling files lack nonce validation code for admin actions

The environment is affected if Link Library version 7.5.13 or lower is installed and the plugin processes admin requests without proper CSRF token validation.

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
Upgrade available Upgrade to a release after 7.5.13
Interim mitigation

Upgrade to Link Library version 7.5.14 or later which includes proper anti-CSRF nonce validation for state-changing operations.

Fix this in Link Library Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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