LiveActive security incident?Get immediate response
CVE Record

CVE-2022-2131: OpenKM XXE Injection

OpenKM 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.

HighCVSS 8.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

OpenKM Community Edition 6.3.10 and earlier can process XML in an unsafe way. An authenticated attacker could abuse this to make the server read external XML entities, potentially exposing sensitive server-side data and causing limited availability impact.

Executive priority

Treat as high priority for affected OpenKM Community systems, especially those exposed to many users or the internet. The main business concern is sensitive data disclosure from the document management server.

Technical view

The issue is CWE-611 XXE in XMLTextExtractor.java, where OpenKM used XMLReader without required security flags. CVSS 3.1 is 8.5: network reachable, low complexity, low privileges required, no user interaction, high confidentiality impact, and low availability impact.

Likely exposure

Organizations running OpenKM Document Management Community Edition 6.3.10 or earlier are the indicated exposure group. The bundle does not identify CPEs, hosted variants, Enterprise Edition impact, or a confirmed fixed version.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source confirms active exploitation. Exploitation requires low privileges, so risk is higher where many users can upload or submit documents for server-side text extraction.

Researcher notes

Evidence supports XXE in OpenKM Community Edition 6.3.10 and before. Sources do not provide exploit details, CPEs, active exploitation evidence, or a named fixed release, so validation should stay tied to version and parser behavior.

Mitigation direction

  • Inventory OpenKM Community Edition deployments and identify versions 6.3.10 or earlier.
  • Review OpenKM and INCIBE guidance for fixed versions or vendor-approved remediation.
  • Restrict document upload and XML-processing access to trusted users until remediated.
  • Limit server egress where feasible to reduce XXE-related external entity retrieval risk.
  • Prioritize remediation on internet-facing or broadly accessible OpenKM instances.

Validation and detection

  • Confirm installed OpenKM edition and version on each deployment.
  • Identify whether XMLTextExtractor.java uses XMLReader with external entity protections enabled.
  • Review application logs for unusual document ingestion by low-privilege accounts.
  • Verify access controls around upload, import, and text extraction workflows.
  • Retest after remediation to confirm unsafe external entity processing is blocked.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-611: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-2131 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L3.14.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.5High
CVSS 3.1 vector shape for CVE-2022-2131Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OpenKMOpenKM Document Management Community6.3.10Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-611 · source CWE mapping

Improper Restriction of XML External Entity Reference

Improper Restriction of XML External Entity Reference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.