CVE-2026-42150: wlc Package Cross-Site Scripting Vulnerability Due to HTML Output

wlc Updated 05 May 2026

Summary

24/04/2026
Yes i
Moderate
5.1

CVE-2026-42150: wlc: print_html outputs API data without HTML escaping. Affects wlc versions < 2.0.0. Fixed in 2.0.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The 'wlc' package is a web-based localization tool that facilitates the translation of software projects. It allows developers to manage and collaborate on translations efficiently. However, a critical vulnerability has been identified in its HTML output functionality, which can lead to security risks if not addressed.

Vulnerability Detail

The vulnerability arises from the 'print_html' function in the wlc package, which outputs API response data directly into HTML without proper escaping. This oversight can lead to cross-site scripting (XSS) attacks when the output is rendered in a web browser. Attackers can exploit this flaw to inject malicious scripts, potentially compromising user data and application integrity.

How To Fix

Latest published version: 3.1.0 as of 23 Oct 2026

pip install --upgrade "wlc==3.1.0"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.0.0

This is the first release that contains the fix.

pip install --upgrade "wlc==2.0.0"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, avoid using the HTML output feature of the wlc package, as the vulnerable code path is opt-in. This means that if you do not explicitly request HTML output, your application will not be affected by this vulnerability.

Conclusion

The wlc package has a vulnerability that can lead to cross-site scripting attacks due to improper handling of HTML output. It is crucial to update to the latest version to mitigate this risk. Users should also consider using Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for wlc →

Share this vulnerability

FAQ

The vulnerability allows for cross-site scripting (XSS) due to unescaped API response data being embedded in HTML.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

The CVSS score for this vulnerability is 5.1, indicating a moderate severity level.

Yes, the vulnerability has been patched in version 2.0.0 of the wlc package. It is recommended to update to this version.

If an immediate update is not possible, refrain from using the HTML output feature of the wlc package as a temporary workaround.

Related vulnerabilities

Recent vulnerabilities recorded for wlc.

How To Fix

Latest published version: 3.1.0 as of 23 Oct 2026

pip install --upgrade "wlc==3.1.0"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.0.0

This is the first release that contains the fix.

pip install --upgrade "wlc==2.0.0"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback