CVE-2026-42150

MEDIUMNVD 5.15.1
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.1 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 93% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

wlc is a Weblate command-line client using Weblate's REST API. Prior to version 2.0.0, the HTML output format in wlc embeds API response data into HTML without escaping, allowing cross-site scripting when the output is rendered in a browser. This issue has been patched in version 2.0.0.

CVSS v3
5.1
EG Score
5.1(medium)
EG Risk
23(Track)
EG Risk 23/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity51% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

May 8, 2026

Last Modified

May 12, 2026

Advisory Details (4)

Auto-updated May 8, 2026
Patch available. Sources: github.
github Patch Available

print_html outputs API data without HTML escaping, enabling stored XSS · Advisory · WeblateOrg/wlc · GitHub

https://github.com/WeblateOrg/wlc/security/advisories/GHSA-gx2m-mcc2-r4p3
generic

Release 2.0.0 · WeblateOrg/wlc · GitHub

https://github.com/WeblateOrg/wlc/releases/tag/2.0.0
generic

fix(output): properly escape generated HTML by nijel · Pull Request #1327 · WeblateOrg/wlc · GitHub

https://github.com/WeblateOrg/wlc/pull/1327
generic

fix(output): properly escape generated HTML (#1327) · WeblateOrg/wlc@0f3e58f · GitHub

https://github.com/WeblateOrg/wlc/commit/0f3e58f6d7457b05d48ef40f579a172c4c8b8469

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
wlc1.13-1 ... 2.0.0-1 (10 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
wlc1.13-2 ... 2.0.0-1 (7 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
wlc1.15-1, 1.15-2, 1.16.1-1, 1.17.2-1, 2.0.0-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
wlc1.15-1, 1.15-2, 1.16.1-1, 1.17.2-12.0.0-1
PyPI(1)
PackageVulnerable rangeFixed inDependents
wlc0.0 ... 1.9 (31 versions)2.0.0

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 133 total refreshes for this CVE.

  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-23 19:30 UTCEG score recompute
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-20 22:55 UTCEPSS rescore
  7. 2026-08-19 17:03 UTCEPSS rescore
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-17 11:59 UTCEG score recompute
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 04:41 UTCEG score recompute
  12. 2026-08-16 02:14 UTCEPSS rescore
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 03:16 UTCEG score recompute
  15. 2026-08-13 22:00 UTCEPSS rescore
  16. 2026-08-13 01:46 UTCEG score recompute
  17. 2026-08-12 13:51 UTCEPSS rescore
  18. 2026-08-12 01:57 UTCEG score recompute
  19. 2026-08-11 13:43 UTCEPSS rescore
  20. 2026-08-11 02:07 UTCEG score recompute
  21. 2026-08-11 00:00 UTCEPSS rescore
  22. 2026-08-10 02:17 UTCEG score recompute
  23. 2026-08-09 13:46 UTCEPSS rescore
  24. 2026-08-09 02:27 UTCEG score recompute
  25. 2026-08-08 16:37 UTCEPSS rescore
Show 75 more
  1. 2026-08-08 01:36 UTCEG score recompute
  2. 2026-08-07 01:47 UTCEG score recompute
  3. 2026-08-06 13:46 UTCEPSS rescore
  4. 2026-08-05 22:12 UTCEG score recompute
  5. 2026-08-05 19:17 UTCEPSS rescore
  6. 2026-08-04 15:10 UTCEPSS rescore
  7. 2026-08-04 10:38 UTCEPSS rescore
  8. 2026-08-04 04:23 UTCEG score recompute
  9. 2026-08-03 10:36 UTCEPSS rescore
  10. 2026-08-02 04:25 UTCEG score recompute
  11. 2026-08-02 02:27 UTCEPSS rescore
  12. 2026-08-01 04:16 UTCEPSS rescore
  13. 2026-07-30 16:28 UTCEPSS rescore
  14. 2026-07-30 01:30 UTCEPSS rescore
  15. 2026-07-28 15:36 UTCEPSS rescore
  16. 2026-07-27 14:13 UTCEPSS rescore
  17. 2026-07-26 14:54 UTCEPSS rescore
  18. 2026-07-26 14:54 UTCEPSS rescore
  19. 2026-07-24 14:17 UTCEPSS rescore
  20. 2026-07-23 14:18 UTCEPSS rescore
  21. 2026-07-23 03:11 UTCEG score recompute
  22. 2026-07-22 14:08 UTCEPSS rescore
  23. 2026-07-21 15:24 UTCEPSS rescore
  24. 2026-07-20 17:08 UTCEPSS rescore
  25. 2026-07-19 14:31 UTCEPSS rescore
  26. 2026-07-19 02:29 UTCEPSS rescore
  27. 2026-07-18 10:04 UTCEPSS rescore
  28. 2026-07-16 17:03 UTCEPSS rescore
  29. 2026-07-16 09:53 UTCOSV refresh
  30. 2026-07-15 16:57 UTCEPSS rescore
  31. 2026-07-15 02:00 UTCEPSS rescore
  32. 2026-07-13 22:30 UTCEPSS rescore
  33. 2026-07-13 06:13 UTCEPSS rescore
  34. 2026-07-13 06:13 UTCEPSS rescore
  35. 2026-07-12 05:46 UTCEPSS rescore
  36. 2026-07-11 08:27 UTCEPSS rescore
  37. 2026-07-09 19:10 UTCEPSS rescore
  38. 2026-07-08 15:15 UTCEPSS rescore
  39. 2026-07-07 13:46 UTCEPSS rescore
  40. 2026-07-06 16:27 UTCEPSS rescore
  41. 2026-07-06 16:27 UTCEPSS rescore
  42. 2026-07-06 02:23 UTCEPSS rescore
  43. 2026-07-06 02:23 UTCEPSS rescore
  44. 2026-07-05 02:30 UTCEPSS rescore
  45. 2026-07-04 06:31 UTCEPSS rescore
  46. 2026-07-01 15:06 UTCEPSS rescore
  47. 2026-06-30 23:22 UTCEPSS rescore
  48. 2026-06-29 14:06 UTCEPSS rescore
  49. 2026-06-28 14:07 UTCEPSS rescore
  50. 2026-06-28 04:56 UTCEPSS rescore
  51. 2026-06-27 03:08 UTCEPSS rescore
  52. 2026-06-25 13:49 UTCEPSS rescore
  53. 2026-06-25 13:49 UTCEPSS rescore
  54. 2026-06-24 14:05 UTCEPSS rescore
  55. 2026-06-23 21:33 UTCEPSS rescore
  56. 2026-06-22 14:25 UTCEPSS rescore
  57. 2026-06-22 14:25 UTCEPSS rescore
  58. 2026-06-21 14:56 UTCEPSS rescore
  59. 2026-06-21 14:56 UTCEPSS rescore
  60. 2026-06-21 01:59 UTCEPSS rescore
  61. 2026-06-19 19:25 UTCEPSS rescore
  62. 2026-06-18 17:52 UTCEPSS rescore
  63. 2026-06-18 17:52 UTCEPSS rescore
  64. 2026-06-17 17:53 UTCEPSS rescore
  65. 2026-06-16 17:52 UTCEPSS rescore
  66. 2026-06-15 17:49 UTCEPSS rescore
  67. 2026-06-13 23:00 UTCEPSS rescore
  68. 2026-06-12 23:12 UTCEPSS rescore
  69. 2026-06-12 23:12 UTCEPSS rescore
  70. 2026-06-11 14:00 UTCEPSS rescore
  71. 2026-06-10 22:18 UTCEPSS rescore
  72. 2026-06-10 13:22 UTCEPSS rescore
  73. 2026-06-10 13:22 UTCEPSS rescore
  74. 2026-06-08 14:17 UTCEPSS rescore
  75. 2026-06-08 14:17 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-42150?
CVE-2026-42150 is a medium vulnerability published on May 8, 2026. wlc is a Weblate command-line client using Weblate's REST API. Prior to version 2.0.0, the HTML output format in wlc embeds API response data into HTML without escaping, allowing cross-site scripting when the output is rendered in a browser. This issue has been patched in version 2.0.0.
When was CVE-2026-42150 disclosed?
CVE-2026-42150 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on May 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42150 actively exploited?
CVE-2026-42150 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.2% of all scored CVEs.
What is the CVSS score of CVE-2026-42150?
CVE-2026-42150 has a CVSS v3 base score of 5.1 (NVD).
How do I remediate CVE-2026-42150?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42150, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-42150

Explore →

Is Your Infrastructure Affected by CVE-2026-42150?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.