dbcve.org
Link LibraryWordPress extension · Ylefebvre

CVE-2024-29123

MEDIUM · 6.1 CVSS v3.1 Published 2024-03-19
Fix available
A fix is available. Upgrade to 7.6.1 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 ('Cross-site Scripting') vulnerability in Yannick Lefebvre Link Library allows Reflected XSS.This issue affects Link Library: from n/a through 7.6.

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

A reflected Cross-site Scripting (XSS) vulnerability exists in the WordPress Link Library plugin (versions through 7.6). The flaw allows unauthenticated attackers to inject malicious JavaScript through unsanitized input parameters, which gets executed in the victim's browser when they click a crafted link. This is a medium-severity issue requiring user interaction (social engineering) to trigger.

MitigationUpgrade Link Library to version 7.7 or later. Until then, implement WAF rules to block XSS attack patterns and warn users not to click untrusted links pointing to the affected site.

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.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
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. Confirm WordPress installation
    Inspect the site for WordPress-specific markers: check for /wp-content/ directory in page source, look for WordPress meta tags in HTML head, or check for wp-admin/ or wp-login.php paths
    Affected if The target site is built on WordPress, which is required for this plugin vulnerability to apply
  2. Verify Link Library plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'link-library' or query the site's plugins via WordPress admin API or database
    Affected if The Link Library plugin by Ylefebvre is installed on the WordPress site
  3. Determine installed Link Library version
    Check the plugin's main PHP file header (usually link-library.php) for the 'Version' comment, or query the wp_options table for the 'link_library_version' option value
    Affected if The installed version is below 7.6.1 (versions through 7.6 are affected)
  4. Confirm plugin is active
    Query the wp_options table where option_name='active_plugins' to verify link-library is in the active list, or attempt to access plugin functionality on the frontend
    Affected if The plugin is active and accessible to visitors, exposing the vulnerable parameters

The environment is affected if WordPress is running with Link Library plugin version 7.6 or earlier that is active, allowing unsanitized input parameters to be exploited for reflected XSS when users click socially engineered links.

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.1 or later
Fixed in 7.6.1
Interim mitigation

Upgrade Link Library to version 7.7 or later. Until then, implement WAF rules to block XSS attack patterns and warn users not to click untrusted links pointing to the affected site.

Recommended fix High confidence

Link Library version 7.6.1 or later

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. Locate Link Library in the list of installed plugins
  4. Click 'Update now' when an update is available, or manually update to version 7.6.1 or later
  5. Verify the plugin version displays 7.6.1 or higher after the update completes

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 / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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