CVE-2023-29043
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 · uneditedPresentations may contain references to images, which are user-controlled, and could include malicious script code that is being processed when editing a document. Script code embedded in malicious documents could be executed in the context of the user editing the document when performing certain actions, like copying content. The relevant attribute does now get encoded to avoid the possibility of executing script code. 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 · high confidenceThis is a cross-site scripting (XSS) vulnerability in presentation software (likely LibreOffice Impress) where user-controlled image references within documents can contain malicious script code. When editing the document and performing actions like copying content, the embedded script executes in the context of the user's session. The fix involves encoding the relevant attribute to prevent script execution.
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.
-
Identify the installed Open Xchange Appsuite versionCheck the version of Open Xchange Appsuite installed in your environment. This is typically found in the product's about page, admin console, or by querying the package manager if installed via OS packages. Look for version information in the server management interface or by running: rpm -q ox-appsuite or similar package query command for your installation method.Affected if The installed version is 7.10.6 or any version lower than 7.10.6 (e.g., 7.10.5, 7.10.4, etc.)
-
Confirm presentation editing functionality is in useVerify that the Open Xchange Appsuite presentation/document editing module is enabled and accessible to users. Check the server configuration or admin panel for enabled appsuite components.Affected if The presentation editing feature is enabled and users can create or edit presentation documents within the appsuite interface
-
Inspect document handling of image referencesThis vulnerability is triggered when a presentation document contains a crafted image reference with embedded script. There is no simple config file to check; the vulnerability exists in the document processing code itself. If you have access to document previews or the underlying document storage, you could examine presentation files for image tag attributes, but this requires manual analysis of individual documents.Affected if Users are opening or editing presentation documents from external or untrusted sources that may contain malicious image references
Your environment is affected if the installed Open Xchange Appsuite version is 7.10.6 or any version lower than 7.10.6, and users have access to the presentation editing functionality.
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.
From vendor data7.10.6
Ensure the software patch encoding the vulnerable image attribute is applied; avoid opening untrusted presentation files from unknown sources until the update is installed.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29043 — 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-2023-29043 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