CVE-2022-40004
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 · uneditedCross Site Scripting (XSS) vulnerability in Things Board 3.4.1 allows remote attackers to escalate privilege via crafted URL to the Audit Log.
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 confidenceCross Site Scripting (XSS) vulnerability in ThingsBoard 3.4.1 in the Audit Log feature allows remote attackers to inject malicious scripts via crafted URLs. The XSS can be leveraged for privilege escalation, potentially allowing attackers to execute actions with elevated permissions or steal session credentials of higher-privileged users.
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= 3.4.1CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
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 ThingsBoard installation and versionAccess the ThingsBoard administration interface (typically at /ui/admin) or query the system info API endpoint. The version is usually displayed in the admin dashboard or can be retrieved via REST API call to /api/versioninfo.Affected if The installed version is exactly 3.4.1.
-
Verify Audit Log feature is accessibleNavigate to the Audit Log section in the ThingsBoard UI (usually under the 'Audit' or 'Administration' menu). Confirm the feature is enabled and accessible to your user account.Affected if The Audit Log feature is enabled and accessible in the environment.
-
Check for suspicious URL parameters in audit logsReview recent audit log entries, particularly those showing URL parameters. Look for entries containing JavaScript tags (<script>), event handlers (onload, onerror, onclick), or encoded characters that could represent XSS payloads.Affected if Audit log entries contain suspicious URL parameters with XSS-like patterns or encoded script content.
-
Inspect for unauthorized privilege escalation indicatorsReview audit logs for actions performed with elevated permissions that were not initiated by the legitimate admin account. Check for user permission changes, API key creation, or dashboard modifications occurring outside normal administrative activity.Affected if Audit logs show privilege escalation actions or unauthorized administrative changes that were not performed by known administrators.
You are affected if your ThingsBoard installation is exactly version 3.4.1 and the Audit Log feature is accessible, as this specific version contains the XSS vulnerability in that component.
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 dataUpgrade ThingsBoard to the latest version or apply vendor-provided security patches. Implement robust input validation and output encoding on all Audit Log parameters, and configure Content Security Policy (CSP) headers to mitigate XSS risks.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40004 — 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-2022-40004 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