dbcve.org
Ox App SuiteApplication · Open Xchange

CVE-2023-24602

MEDIUM · 6.1 CVSS v3.1 Published 2023-05-29
Fix available
A fix is available. Upgrade to 7.10.6 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
OX App Suite before frontend 7.10.6-rev24 allows XSS via data to the Tumblr portal widget, such as a post title.

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 OX App Suite's Tumblr portal widget allows injection of malicious scripts via unsanitized post title data. The vulnerability affects versions before frontend 7.10.6-rev24, enabling attackers to execute arbitrary JavaScript in the context of user sessions.

MitigationUpgrade OX App Suite frontend to version 7.10.6-rev24 or later. Additionally, implement output encoding and input validation on the Tumblr widget to prevent XSS attacks until the patch is applied.

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:< 7.10.6= 7.10.6

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 frontend version
    Check the installed frontend package version via the admin panel, package manager, or version file (typically found in /opt/open-xchange or similar installation directories). Look for a file named version or manifest that lists the frontend build revision.
    Affected if The installed frontend version is below 7.10.6-rev24 (including any 7.10.6 release).
  2. Confirm Tumblr portal widget is enabled
    Access the OX App Suite admin interface and navigate to the portal/ widget configuration section. Verify whether the Tumblr widget is listed as an available or active portal widget for users.
    Affected if The Tumblr widget is enabled or available in the portal configuration.
  3. Check for Tumblr widget usage in user sessions
    Review user portal configurations or check if any users have added the Tumblr widget to their personal dashboard. This may be visible in user preferences or admin audit logs.
    Affected if Users have the Tumblr widget configured or active in their portal.

A user is affected if their OX App Suite frontend version is below 7.10.6-rev24 AND the Tumblr portal widget is enabled and accessible to users in their environment.

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

Upgrade OX App Suite frontend to version 7.10.6-rev24 or later. Additionally, implement output encoding and input validation on the Tumblr widget to prevent XSS attacks until the patch is applied.

Recommended fix Moderate confidence

OX App Suite frontend 7.10.6-rev24 or later (including 7.10.7 and subsequent stable releases)

  1. 1. Identify the current OX App Suite frontend version installed in your environment.
  2. 2. Check if the current version is older than 7.10.6-rev24 or is exactly 7.10.6 without the rev24 patch.
  3. 3. If affected, plan for an upgrade to a version that includes the fix (7.10.6-rev24 or later, or the next stable release 7.10.7 and above).
  4. 4. Coordinate with your operations team to schedule a maintenance window for the upgrade.
  5. 5. Before applying in production, test the upgrade in a staging environment to verify the fix and ensure no regressions.
  6. 6. Apply the upgrade following standard OX App Suite upgrade procedures.
  7. 7. After upgrade, verify that the Tumblr portal widget properly sanitizes input and no longer allows XSS.
Caveat Review OX App Suite release notes for any breaking changes between your current version and the target version before upgrading

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

Fix this in Ox App Suite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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