CVE-2026-38429
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 · uneditedOpenCMS v20 and before is vulnerable to XML External Entity (XXE) in the Admin Import DB feature due to insecure XML parsing of user supplied .zip files containing a manifest.xml.
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 confidenceOpenCMS v20 and earlier contains an XML External Entity (XXE) vulnerability in the Admin Import DB feature. The application parses manifest.xml files from user-supplied ZIP archives without disabling external entity processing, allowing attackers to inject malicious entity references that can read local files, perform SSRF attacks, or cause denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Confirm OpenCMS versionLocate the OpenCMS installation directory and check the version file or dashboard. Common locations include: version.txt in the installation root, or the 'About' section in the Admin panel.Affected if The installed version is v20 or any version before v20 (e.g., v19, v18, older releases).
-
Verify Admin Import DB feature accessLog in to the OpenCMS administrative interface and navigate to the database import functionality. Typically found under Administration > Database > Import or similar path depending on the UI structure.Affected if The Admin Import DB feature is present and accessible to the user account being used.
-
Check XML parser configuration for external entitiesInspect the OpenCMS configuration files (such as web.xml, OpenCms.xml, or custom XML handler configurations) for the XML parser settings used by the import feature. Look for parser properties that control external entity processing.Affected if The XML parser configuration does not explicitly disable external entity processing (e.g., no 'external-general-entities' or 'external-parameter-entities' set to false, or no custom entity resolver restricting external access).
A user is affected if they are running OpenCMS v20 or earlier AND the Admin Import DB feature is accessible, with the XML parser not configured to disable external entity processing.
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 dataDisable XML external entity (XXE) processing in the XML parser configuration and implement strict validation of uploaded ZIP files before parsing any contained XML, including verifying the manifest.xml structure and rejecting files with external entity declarations.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-38429 — 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-2026-38429 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