CVE-2022-43697
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 · uneditedOX App Suite before 7.10.6-rev30 allows XSS via an activity tracking adapter defined by jslob.
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 confidenceOX App Suite before 7.10.6-rev30 contains a Cross-Site Scripting (XSS) vulnerability in the activity tracking adapter functionality, which is configurable through jslob (JavaScript Library Object). Attackers can inject malicious scripts through the jslob-defined activity tracking adapter that execute in users' browsers when they interact with the affected component.
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< 7.10.6= 7.10.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine OX App Suite versionAccess the admin panel or run the appropriate version check command for your OX App Suite installation. Common methods include checking the package manager or accessing the /manifest endpoint if available.Affected if The installed version is any version before 7.10.6-rev30, or exactly 7.10.6 (without the -rev30 suffix).
-
Locate jslob configurationIdentify the jslob (JavaScript Library Object) configuration files or database entries for your OX App Suite installation. These are typically stored in the configuration database or in /opt/open-xchange/etc/settings directory.Affected if jslob configuration files or entries exist in the environment.
-
Inspect activity tracking adapter settingsExamine the jslob configuration for the activity tracking adapter. Look for settings related to 'io.ox/mail/activityTracking' or similar activity tracking paths in the jslob tree.Affected if The activity tracking adapter is enabled or configured in jslob with any non-empty value.
-
Verify mail plugin statusCheck if the mail plugin is enabled in OX App Suite, as the activity tracking adapter typically interacts with mail-related components.Affected if The mail plugin is active and the activity tracking feature is in use.
You are affected if your OX App Suite version is below 7.10.6-rev30 (or is exactly 7.10.6) AND the jslob-based activity tracking adapter is enabled in your configuration.
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 · scoped7.10.6
Upgrade OX App Suite to version 7.10.6-rev30 or later to patch the XSS vulnerability in the activity tracking adapter. Alternatively, restrict or disable the jslob-based activity tracking configuration if upgrading is not immediately feasible.
7.10.6-rev30 or later
- Upgrade OX App Suite to version 7.10.6-rev30 or later
- After upgrade, verify the fix by testing that the jslob-defined activity tracking adapter no longer accepts unsanitized input
- Confirm the version number post-upgrade matches or exceeds 7.10.6-rev30
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43697 — 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-43697 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