CVE-2022-2131
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 · uneditedOpenKM Community Edition in its 6.3.10 version and before was using XMLReader parser in XMLTextExtractor.java file without the required security flags, allowing an attacker to perform a XML external entity injection attack.
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 confidenceOpenKM Community Edition 6.3.10 and prior contains an XML External Entity (XXE) injection vulnerability in XMLTextExtractor.java. The XMLReader parser is used without disabling external entity processing, allowing attackers to inject malicious XML to read local files, perform SSRF, or cause denial of service.
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<= 6.3.10CVSS 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.
-
Identify OpenKM installation and versionLocate the OpenKM installation directory and check the version manifest or about page. Common locations include /opt/openkm or within application servers. Look for version files or check the application metadata.Affected if The installed version is OpenKM Community Edition 6.3.10 or any prior version (e.g., 6.3.9, 6.3.8, etc.)
-
Locate the XMLTextExtractor componentSearch for the file XMLTextExtractor.java or its compiled class in the OpenKM installation directories, typically under src/ or in the WEB-INF/lib/classes path.Affected if The XMLTextExtractor component exists in the installation and is being used for XML text extraction functionality
-
Check XMLReader configuration in the extractorExamine the XMLTextExtractor source code or decompiled class for the XMLReader initialization. Look for whether external-general-entities and external-parameter-entities are explicitly set to false, or if security features are configured.Affected if The XMLReader is instantiated without disabling external entity processing (no setFeature for external entities set to false)
-
Verify XML file processing is enabledConfirm that OpenKM is configured to accept and process XML file uploads, or that the XMLTextExtractor is used for document content indexing.Affected if XML file processing or text extraction features are active in the OpenKM deployment
You are affected if you run OpenKM Community Edition version 6.3.10 or prior and use the XMLTextExtractor to process XML files without custom secure XMLReader 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.
From vendor dataConfigure XMLReader with security features disabled for external entities and DTD processing (set external-general-entities and external-parameter-entities to false), or use a secure XMLInputFactory configuration.
- Consultation2.0 h
- Implementation2.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2131 — 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-2131 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