CVE-2022-43696
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-rev20 allows XSS via upsell ads.
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 confidenceCross-site scripting (XSS) vulnerability in OX App Suite's upsell advertisements feature. The vulnerability allows attackers to inject malicious scripts through unsanitized input in ads displayed to users, potentially leading to session hijacking or unauthorized actions performed in the context of victim users.
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 installed OX App Suite versionUse the package manager or OX-specific version command to retrieve the installed OX App Suite version (e.g., rpm -q ox-app-suite or check the admin UI for version information)Affected if The installed version is < 7.10.6 or exactly 7.10.6 (versions prior to 7.10.6-rev20)
-
Verify upsell advertisement feature is enabledInspect the OX App Suite configuration files or admin settings for the upsell/upsell-ads module. This may be found in configuration files under /opt/open-xchange/etc or via the admin panel under bundled apps or marketplace settingsAffected if The upsell advertisements feature is enabled and active in the configuration
-
Review ad-related configuration for unsanitized input pathsExamine any configuration files controlling the upsell ad content delivery (often in properties or YAML files under the ads or marketing directory). Look for settings that define ad sources or custom ad contentAffected if Custom or external ad sources are configured without proper sanitization checks
-
Check for recent XSS-related incidentsReview server and web access logs for suspicious script injection patterns in requests related to ad-serving endpoints (look for <script>, javascript:, onerror, or similar XSS payloads)
Your environment is affected if OX App Suite version is less than 7.10.6-rev20 (or equals 7.10.6) AND the upsell advertisement feature is enabled.
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
Update OX App Suite to version 7.10.6-rev20 or later, which includes proper input sanitization for the upsell ads component. If immediate patching is not possible, consider disabling or restricting upsell ad functionality until the update can be applied.
7.10.6-rev20 or later
- Identify your current OX App Suite version using the admin dashboard or command-line tools
- Download OX App Suite version 7.10.6-rev20 or later from the Open-Xchange customer portal or official download channels
- Review the Open-Xchange upgrade documentation for 7.10.6-rev20
- Execute the upgrade process according to Open-Xchange upgrade procedures, typically involving stopping the services, running the installer, and restarting services
- Verify the upgrade was successful by checking the version number and confirming the XSS vulnerability is resolved by testing the upsell ads functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43696 — 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-43696 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