CVE-2022-30289
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 · uneditedA stored Cross-site Scripting (XSS) vulnerability was identified in the Data Import functionality of OpenCTI through 5.2.4. An attacker can abuse the vulnerability to upload a malicious file that will then be executed by a victim when they open the file location.
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 confidenceA stored Cross-site Scripting (XSS) vulnerability exists in OpenCTI's Data Import functionality through version 5.2.4. Attackers can upload malicious files containing XSS payloads that persist on the server. The payload executes when a victim opens or accesses the file location within the application, as the file path/name is rendered without proper output encoding.
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<= 5.2.4CVSS 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.
-
Identify OpenCTI versionCheck the installed OpenCTI version by reviewing the application About page, docker image tags, or package manager metadata. Compare against the affected range <= 5.2.4.Affected if The installed version is 5.2.4 or lower.
-
Confirm Data Import is accessibleDetermine whether the Data Import functionality is enabled for your OpenCTI instance. This feature allows users to import indicators, threat actors, and other threat intelligence data.Affected if Data Import feature is enabled and accessible to users.
-
Locate import file storageIdentify where uploaded files are stored on the server. Common locations include data directories, upload folders, or container volumes used by the OpenCTI platform.Affected if File storage directories exist and are accessible.
-
Inspect uploaded filenames for XSS payloadsExamine filenames in the import directory for suspicious patterns such as <script> tags, javascript: URLs, onload/onerror event handlers, or other HTML/JS injection attempts.Affected if Any uploaded file contains an XSS payload in its filename that would execute when rendered in the browser.
You are affected if running OpenCTI version 5.2.4 or lower with Data Import functionality enabled and any maliciously crafted filename exists in the upload directory.
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 · scopedImplement strict input validation on file uploads (allowlist approved file types, sanitize filenames) and ensure all file metadata and paths are properly output-encoded before rendering in the browser to prevent script execution.
OpenCTI 5.2.5 or later stable release
- Backup your OpenCTI instance and database before proceeding with any upgrade
- Check the official OpenCTI GitHub releases page (github.com) for version 5.2.5 or later to confirm the fix for CVE-2022-30289
- Upgrade OpenCTI to version 5.2.5 or the latest stable release available
- After upgrade, verify the Data Import functionality works correctly and that uploaded files are properly sanitized
- Test that the XSS payload used in the attack is now properly escaped/neutralized when files are accessed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30289 — 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-30289 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