CVE-2023-26559
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 · uneditedA directory traversal vulnerability in Oxygen XML Web Author before 25.0.0.3 build 2023021715 and Oxygen Content Fusion before 5.0.3 build 2023022015 allows an attacker to read files from a WEB-INF directory via a crafted HTTP request. (XML Web Author 24.1.0.3 build 2023021714 and 23.1.1.4 build 2023021715 are also fixed versions.)
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 confidenceA directory traversal vulnerability in Oxygen XML Web Author and Oxygen Content Fusion allows unauthenticated attackers to read arbitrary files from the WEB-INF directory via specially crafted HTTP requests containing path traversal sequences (e.g., ../../../WEB-INF). This could expose sensitive configuration files, application source code, or other confidential data.
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< 5.0.3< 23.1.1.4>= 24.0.0.0, < 24.1.0.3>= 25.0.0.0, < 25.1.0.3CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 installed Oxygen productLocate the Oxygen XML Web Author or Oxygen Content Fusion installation directory and check for version.txt, about.html, or the product's startup banner which displays the version numberAffected if The product is Oxygen XML Web Author or Oxygen Content Fusion with a version lower than the fixed releases (23.1.1.4, 24.1.0.3, 25.1.0.3 for Web Author; 5.0.3 for Content Fusion)
-
Determine exact version numberOpen the version file in the installation directory or check the application's About dialog / startup banner to obtain the precise build number (e.g., 2023021715)Affected if The version/build number matches one of the vulnerable ranges: < 23.1.1.4; >= 24.0.0.0 and < 24.1.0.3; >= 25.0.0.0 and < 25.1.0.3 for Web Author, or < 5.0.3 for Content Fusion
-
Verify web service is exposedCheck if the Oxygen web application is accessible over HTTP/HTTPS by attempting to reach the server (e.g., curl -I http://hostname:port/)Affected if The web interface is exposed and responds to HTTP requests, making the path traversal attack surface accessible
-
Check server headers for version leakSend an HTTP request to the web server and inspect response headers (curl -v http://hostname:port/) for version information in Server or X-Powered-By headersAffected if The server exposes version information confirming a vulnerable release
You are affected if Oxygen XML Web Author (versions < 23.1.1.4, 24.0.0.0 to 24.1.0.2, or 25.0.0.0 to 25.1.0.2) or Oxygen Content Fusion (versions < 5.0.3) is running and the web interface is accessible over the network.
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 · scoped5.0.323.1.1.424.1.0.3
Upgrade to Oxygen XML Web Author 25.0.0.3 (build 2023021715), 24.1.0.3 (build 2023021714), or 23.1.1.4 (build 2023021715), and Oxygen Content Fusion 5.0.3 (build 2023022015) or later. Additionally, implement input validation to reject HTTP requests containing path traversal patterns.
Oxygen Content Fusion 5.0.3 or Oxygen XML Web Author 23.1.1.4/24.1.0.3/25.0.0.3 (depending on product and version line)
- Identify which Oxygen product is in use: Content Fusion or XML Web Author
- For Oxygen Content Fusion: Upgrade to version 5.0.3 (build 2023022015) or later
- For Oxygen XML Web Author 23.x: Upgrade to version 23.1.1.4 (build 2023021715) or later
- For Oxygen XML Web Author 24.x: Upgrade to version 24.1.0.3 (build 2023021714) or later
- For Oxygen XML Web Author 25.x: Upgrade to version 25.0.0.3 (build 2023021715) or later
- After upgrade, verify the WEB-INF directory is no longer accessible via path traversal requests
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26559 — 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-26559 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