CVE-2022-40605
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 · uneditedMITRE CALDERA before 4.1.0 allows XSS in the Operations tab and/or Debrief plugin via a crafted operation name, a different vulnerability than CVE-2022-40606.
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 · high confidenceMITRE CALDERA before 4.1.0 contains a stored Cross-Site Scripting (XSS) vulnerability in the Operations tab and Debrief plugin. Attackers can inject malicious JavaScript via a crafted operation name that executes when other users view the operation or debrief data. The CVSS 6.1 indicates network-exploitable XSS requiring user interaction to trigger.
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< 4.1.0CVSS 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.
-
Determine CALDERA versionLocate the CALDERA version file or check the application footer/version endpoint. Common locations include a version.py file, VERSION file in the root directory, or the /api/version API endpoint.Affected if The installed version is any version prior to 4.1.0
-
Verify Operations tab accessLog into CALDERA and navigate to the Operations tab in the web interface. Check if you can view or create operations.Affected if The Operations tab is accessible and users can view or create operations in the affected version (< 4.1.0)
-
Verify Debrief plugin statusCheck the Debrief plugin configuration in the plugins directory or via the web interface plugins page. Confirm whether the Debrief plugin is enabled.Affected if The Debrief plugin is enabled in an affected version (< 4.1.0)
-
Inspect existing operation namesList all operations in the Operations tab and examine the operation names for any unusual characters, script tags, or suspicious patterns (e.g., <script>, javascript:, onerror=, onload=).Affected if Any operation name contains raw HTML, script tags, or JavaScript event handlers without proper encoding
You are affected if CALDERA version is below 4.1.0 AND either the Operations tab or Debrief plugin is accessible to users who could view crafted operation names.
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 data4.1.0
Upgrade to CALDERA 4.1.0 or later which includes proper input sanitization and output encoding for operation names. If immediate upgrade is not possible, implement context-aware output encoding for operation name fields in the Operations tab and Debrief plugin.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40605 — 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-40605 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