Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2021-44848: Username Enumeration in Thinfinity VirtualUI /changePassword

Published Dec 13, 2021 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.3Medium · v3.1
EPSS23.0%98th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Cybelesoft
IdentifiersCVE-2021-44848CWE-204

Cibele Thinfinity VirtualUI before version 3.0 contains a vulnerability in the /changePassword endpoint, where the application returns different responses for invalid authentication requests depending on whether the username exists. This allows an attacker to enumerate valid usernames by analyzing the responses to crafted requests.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker can enumerate valid usernames on the system by sending authentication requests to the /changePassword endpoint and observing the differences in responses. This information can be used to facilitate further attacks, such as brute-force or targeted phishing attacks.

Mitigation

If you can’t patch tonight, do this now.

As an interim measure, implement generic error messages for authentication failures and monitor for abnormal activity on the /changePassword endpoint. Consider rate limiting and alerting on repeated failed authentication attempts.

Remediation

Patch, then assume compromise.

Upgrade Thinfinity VirtualUI to version 3.0 or later, where this issue has been addressed. Ensure that authentication endpoints return generic error messages regardless of the validity of the username or password.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
CybelesoftThinfinity Virtualuiapplication
FAQ

Frequently asked questions

Is CVE-2021-44848 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2021-44848 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2021-44848?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2021-44848.
Is there a patch for CVE-2021-44848?
Upgrade Thinfinity VirtualUI to version 3.0 or later, where this issue has been addressed. Ensure that authentication endpoints return generic error messages regardless of the validity of the username or password.
What products are affected by CVE-2021-44848?
Cybelesoft Thinfinity Virtualui.
How severe is CVE-2021-44848?
CVE-2021-44848 has a CVSS v3.1 score of 5.3 (Medium) and an EPSS score of 23.0% (98th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.