CVE-2022-43706
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 the Web UI of StackStorm versions prior to 3.8.0 allowed logged in users with write access to pack rules to inject arbitrary script or HTML that may be executed in Web UI for other logged in users.
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 confidenceA stored Cross-Site Scripting (XSS) vulnerability exists in StackStorm's Web UI where authenticated users with write access to pack rules can inject malicious JavaScript or HTML into rule definitions. When other logged-in users view these rules in the Web UI, the injected script executes in their browser session.
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.8.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Check if StackStorm is installedRun command: which st2 or pip show st2 or look for /opt/stackstorm directoryAffected if StackStorm is not found on the system
-
Determine the installed StackStorm versionRun command: st2 --version or pip show st22-webui | grep VersionAffected if Version is less than 3.8.0
-
Verify the Web UI is enabled and accessibleCheck if the webui service is running: systemctl status st2web or docker ps for web container, and verify port 443 or 8080 is listeningAffected if Web UI is exposed and accessible
-
Identify if pack rules exist in the environmentRun command: st2 rule list --pack=<packname> for each pack, or check /opt/stackstorm/packs/rules/ directory for rule definition filesAffected if Pack rules are present and can be viewed in the Web UI
-
Inspect rule definitions for potential XSS payloadsReview rule definition YAML files in /opt/stackstorm/packs/ for script tags, javascript: URLs, or HTML in rule description, display name, or action parametersAffected if Rule definitions contain unsanitized user-controlled content that could execute in a browser
The environment is affected if StackStorm version is below 3.8.0, the Web UI is accessible, and pack rules exist that may contain injected JavaScript or HTML from untrusted sources.
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.
dbcve · scoped3.8.0
Upgrade StackStorm to version 3.8.0 or later, which contains the fix for this XSS vulnerability in pack rule rendering.
3.8.0
- Upgrade StackStorm to version 3.8.0 or later by following the official upgrade documentation at docs.stackstorm.com
- Verify the upgrade completed successfully by checking the StackStorm services are running
- Confirm the Web UI is accessible and the version displayed reflects 3.8.0 or later
- Test that users with pack rule write access cannot inject arbitrary script or HTML through the rule interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43706 — 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-43706 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