dbcve.org
Bilingual LinkerWordPress extension · Ylefebvre

CVE-2024-13441

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-25
Fix available
A fix is available. Upgrade to 2.4.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
The Bilingual Linker plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the bl_otherlang_link_1 parameter in all versions up to, and including, 2.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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

The Bilingual Linker WordPress plugin versions up to 2.4 fails to properly sanitize and escape the bl_otherlang_link_1 parameter, allowing authenticated users with Contributor-level access or higher to inject malicious JavaScript that executes when other users view affected pages.

MitigationUpdate to version 2.5 or later which includes proper input sanitization and output escaping for affected parameters.

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
Bilingual LinkerWordPress extension
Affected:< 2.4.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 Bilingual Linker plugin is installed
    Navigate to WordPress admin > Plugins or inspect wp-content/plugins/ directory for a folder containing 'bilingual-linker' or 'bilingual-linker'
    Affected if Plugin folder exists in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and look for Bilingual Linker version number, or open the main plugin PHP file (usually bilingual-linker.php) and locate the Version header in the plugin comment block
    Affected if Version is 2.4 or lower (anything below 2.4.1)
  3. Identify if the vulnerable parameter is in use
    Access plugin settings (usually under Settings > Bilingual Linker or similar) and check if the bl_otherlang_link_1 field exists and contains any value
    Affected if The parameter bl_otherlang_link_1 is present in the plugin settings and contains unsanitized input
  4. Inspect stored data for potential XSS payloads
    Query the WordPress database (usually wp_options table) for options containing 'bl_otherlang_link_1' and examine the stored value for script tags or HTML
    Affected if The database contains values with unescaped HTML or JavaScript in fields related to bl_otherlang_link_1

If Bilingual Linker version is 2.4 or below AND the bl_otherlang_link_1 parameter is exposed in the plugin settings, the installation is affected by this stored XSS vulnerability.

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 2.4.1 or later
Fixed in 2.4.1
Interim mitigation

Update to version 2.5 or later which includes proper input sanitization and output escaping for affected parameters.

Recommended fix High confidence

2.4.1

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find the Bilingual Linker plugin
  4. Click 'Update now' if an update is available, or manually update to version 2.4.1
  5. Verify the plugin version shows 2.4.1 after updating

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

Fix this in Bilingual Linker Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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