dbcve.org
IrisApplication · Dfir Iris

CVE-2023-50712

MEDIUM · 5.4 CVSS v3.1 Published 2023-12-22
Fix available
A fix is available. Upgrade to 2.3.7 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Iris is a web collaborative platform aiming to help incident responders sharing technical details during investigations. A stored Cross-Site Scripting (XSS) vulnerability has been identified in iris-web, affecting multiple locations in versions prior to v2.3.7. The vulnerability may allow an attacker to inject malicious scripts into the application, which could then be executed when a user visits the affected locations. This could lead to unauthorized access, data theft, or other related malicious activities. An attacker need to be authenticated on the application to exploit this vulnerability. The issue is fixed in version v2.3.7 of iris-web. No known workarounds are available.

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 confidence

Stored Cross-Site Scripting (XSS) vulnerability in iris-web allows authenticated attackers to inject malicious scripts into multiple application locations. The injected scripts execute when users visit affected pages, potentially leading to session hijacking, data theft, or unauthorized actions performed in the context of legitimate users.

MitigationUpgrade iris-web to version v2.3.7. Conduct post-upgrade validation to confirm all stored XSS vectors have been properly remediated and no residual vulnerabilities remain.

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
IrisApplication
Affected:< 2.3.7

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed iris-web version
    Check the version file or banner - typically found in the application source, Docker image tag, or by querying the application's /api/version endpoint if exposed
    Affected if Version is lower than 2.3.7 (e.g., 2.3.6, 2.3.5, earlier versions)
  2. Verify running version via application metadata
    Review the iris-web source code directory for a VERSION file, or check git tags if deployed from source; for Docker deployments, inspect the image tag or digests
    Affected if Cannot locate version 2.3.7 or higher in the deployment artifacts
  3. Check deployment method
    Identify whether iris-web is deployed via Docker, pip, or source installation - each has different version locations (Dockerfile, requirements.txt, git history)
    Affected if Deployment uses an older version that predates the 2.3.7 release

You are affected if the deployed iris-web version is any release prior to 2.3.7, as the stored XSS vulnerability exists in all earlier versions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.3.7 or later
Fixed in 2.3.7
Interim mitigation

Upgrade iris-web to version v2.3.7. Conduct post-upgrade validation to confirm all stored XSS vectors have been properly remediated and no residual vulnerabilities remain.

Recommended fix High confidence

v2.3.7

  1. Back up the current Iris installation and database before proceeding with the upgrade
  2. Download Iris version v2.3.7 from the official GitHub repository (github.com)
  3. Stop the currently running Iris service
  4. Replace the existing Iris files with the new version v2.3.7 files
  5. Run any database migrations if required by the upgrade (consult release notes for v2.3.7)
  6. Restart the Iris service
  7. Verify the upgrade was successful by logging in and checking the version number

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Iris Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-50712 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-50712 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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