CVE-2021-41943
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 · uneditedLogrhythm Web Console 7.4.9 allows for HTML tag injection through Contextualize Action -> Create a new Contextualize Action -> Inject your HTML tag in the name field.
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 · moderate confidenceThis is a stored HTML injection (Cross-Site Scripting) vulnerability in LogRhythm Web Console 7.4.9. An authenticated attacker can inject malicious HTML/JavaScript through the name field when creating a new Contextualize Action, which will be rendered when other users view the contextualize action, potentially allowing session hijacking or credential theft.
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= 7.4.9CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify LogRhythm Web Console installationLocate the LogRhythm Web Console installation in your environment and identify the installed version. This is typically found in the console's about page, configuration files, or the installer metadata. Consult your LogRhythm documentation for version location methods.Affected if The installed version is LogRhythm Web Console 7.4.9 exactly
-
Confirm version matches affected releaseCompare your identified version against the affected version range. This CVE affects only version 7.4.9 specifically.Affected if Your LogRhythm Web Console version is 7.4.9
-
Verify Contextualize Action feature accessCheck if your LogRhythm Web Console user accounts have access to the Contextualize Action creation functionality. This is typically found within the console's administrative or configuration interfaces. Verify if any users have created contextualize actions.Affected if The Contextualize Action feature exists and has been used in your environment
-
Inspect Contextualize Action name fields for suspicious contentExamine all existing Contextualize Action entries in your system. Review the name field of each action for unusual characters, HTML tags, JavaScript code, or content that does not appear to be legitimate business data. This may require database queries or console administrative tools depending on your deployment.Affected if Any Contextualize Action name field contains HTML tags, script elements, or potentially malicious content
You are affected if your LogRhythm Web Console is exactly version 7.4.9 and you have created Contextualize Actions that could contain injected malicious content.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement strict input validation and output encoding for the name field in the Contextualize Action creation feature. Upgrade to a patched version of LogRhythm Web Console if available from the vendor.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-41943 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-41943 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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