dbcve.org
Ox App SuiteApplication · Open Xchange

CVE-2024-23187

MEDIUM · 6.1 CVSS v3.1 Published 2024-05-06
Fix available
A fix is available. Upgrade to 8.22 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Content-ID based embedding of resources in E-Mails could be abused to trigger client-side script code when using the "show more" option. Attackers could perform malicious API requests or extract information from the users account. Exploiting the vulnerability requires user interaction. Please deploy the provided updates and patch releases. CID replacement has been hardened to omit invalid identifiers. No publicly available exploits are known.

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 confidence

Cross-site scripting (XSS) vulnerability in email client handling of Content-ID (CID) embedded resources. Attackers can embed malicious script code in email attachments using CID, which executes when users click 'show more' to reveal full content, enabling unauthorized API requests or account data extraction. The fix hardens CID replacement logic to filter out invalid identifiers.

MitigationDeploy the vendor-provided patch releases which harden CID replacement to omit invalid identifiers. Test email rendering with the 'show more' functionality after deployment.

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
Ox App SuiteApplication
Affected:< 8.22

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

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

  1. Identify Ox App Suite version
    Locate the installed Ox App Suite version via package manager, admin console, or version check endpoint. Common locations: /opt/open-xchange/version, RPM package query 'rpm -q open-xchange', or admin UI version display.
    Affected if Version is below 8.22 (e.g., 8.20.x, 8.21.x)
  2. Confirm mail module is active
    Check if the email/mail module is provisioned and active for users. Verify via admin console user settings or config database query for mail capability.
    Affected if Mail module is enabled and users can receive/display emails
  3. Verify show more rendering feature
    Determine if the email client's 'show more' content expansion feature is available. This is the trigger point for the CID-based XSS. Check via UI testing or config setting for inline email expansion.
    Affected if Show more / content expansion feature is available in the email client
  4. Inspect CID rendering configuration
    Review email rendering settings related to Content-ID (CID) inline image handling. Check configuration files or API settings governing how CID-referenced attachments are processed.
    Affected if CID-based inline attachment rendering is permitted

User is affected if Ox App Suite version is below 8.22 AND the mail module with show more content expansion is enabled, allowing CID-embedded content to render.

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 8.22 or later
Fixed in 8.22
Interim mitigation

Deploy the vendor-provided patch releases which harden CID replacement to omit invalid identifiers. Test email rendering with the 'show more' functionality after deployment.

Recommended fix High confidence

Ox App Suite 8.22 or later

  1. 1. Identify current Ox App Suite version by checking the installed package or admin console
  2. 2. Plan upgrade to Ox App Suite version 8.22 or later (the fixed release)
  3. 3. Review release notes for version 8.22 to understand changes and ensure compatibility
  4. 4. Test the upgrade in a non-production environment before deploying to production
  5. 5. Execute the upgrade following standard upgrade procedures for Ox App Suite
  6. 6. Verify the CID replacement hardening is active by testing email rendering with Content-ID resources
  7. 7. Confirm the XSS vulnerability is mitigated by validating that invalid identifiers are now omitted
Caveat Review release notes for potential compatibility changes; standard upgrade risks apply

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

Fix this in Ox App Suite Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
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,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23187 — 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-2024-23187 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