Skip to main content
← Vulnerabilities

BlueprintUE Self-Hosted Edition 4.2.0 before 4.3.4 Login Rate Limit Bypass

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

6.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 4.3.4
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 4.3.4.

23Pcve.now Index 23 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Data gap: No advisory context yet
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity6.3/10CVSS 6.3
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 28 if advisories confirm default setups are exposed

CVE-2026-122138 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.3 (medium) and affects blueprintue-self-hosted-edition; fixed in 4.3.4.

Published
Last modified
Published
Not listed in CISA KEV
23/100 · provisional
Fix
Fixed in 4.3.4
None on Exploit-DB, Metasploit or GitHub

Summary

BlueprintUE Self-Hosted Edition has a login rate limit bypass in its LoginMiddleware component, where failed-login counters are keyed on case-sensitive usernames. An attacker can reach it remotely, without logging in, by varying the casing of a username to get extra password attempts and brute-force past the per-account lockout.

Read the original description

BlueprintUE Self-Hosted Edition 4.2.0 before 4.3.4 contains a login rate limit bypass vulnerability in LoginMiddleware.php that keys failed-login counters on case-sensitive usernames. Unauthenticated attackers can vary username casing against case-insensitive MySQL lookups to get extra attempts and brute-force passwords past the per-account lockout.

What to do

  • Upgrade to a fixed version: 4.3.4.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • blueprintue blueprintue-self-hosted-edition

    From 4.2.0 · fixed in 4.3.4

Evidence 6

  1. Advisory
  2. Patch
  3. Patch
  4. Repository
  5. Repository
  6. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-122138

Is CVE-2026-122138 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-122138?

blueprintue-self-hosted-edition: from 4.2.0 before 4.3.4.Source: cve.now feed data

How do I fix CVE-2026-122138?

Upgrade to a fixed version: 4.3.4.Source: cve.now feed data