LiveActive security incident?Get immediate response
CVE Record

CVE-2021-33950: An issue discovered in OpenKM v6.3.10 allows attackers to obtain sensitive information via the XMLTextExtra...

An issue discovered in OpenKM v6.3.10 allows attackers to obtain sensitive information via the XMLTextExtractor function.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-33950 is a high-severity information disclosure issue reported in OpenKM v6.3.10. The vulnerable XMLTextExtractor function may expose sensitive information. The source bundle links upstream issue, pull request, and commit evidence, but does not name a fixed release.

Executive priority

Treat this as a high-priority confidentiality risk for any OpenKM v6.3.10 environment. Prioritize internet-facing or untrusted-document workflows first, but avoid emergency claims without exploitation evidence.

Technical view

The CVE describes a CWE-611 weakness in OpenKM v6.3.10 involving XMLTextExtractor. CVSS 3.1 is 7.5: network reachable, low complexity, no privileges, no user interaction, with high confidentiality impact and no integrity or availability impact.

Likely exposure

Exposure is most likely in organizations running OpenKM v6.3.10, especially where XML or document extraction workflows process untrusted content. The source bundle’s structured affected-product metadata is incomplete.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates remote unauthenticated attack potential, but exploit availability is not established here.

Researcher notes

CWE-611 points to XML external entity handling. The upstream commit and PR are the key remediation artifacts. The bundle lacks a fixed version, affected CPEs, and exploitation evidence, so validation should be code- and deployment-focused.

Mitigation direction

  • Inventory OpenKM deployments and confirm whether v6.3.10 is present.
  • Review upstream PR, issue, and commit for the vendor project fix.
  • Apply the project fix or a vendor-supported release containing it.
  • Restrict untrusted document processing until remediation is confirmed.
  • Monitor vendor guidance for a named fixed version.

Validation and detection

  • Confirm XMLTextExtractor code includes the upstream remediation commit.
  • Verify deployed OpenKM version and build provenance.
  • Review logs for suspicious document extraction failures or unusual XML processing activity.
  • Confirm external entity processing is disabled in relevant XML parser paths.
  • Retest document ingestion safely after applying the fix.
Prepared
Confidence
medium
Sources
5

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-2021-33950 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
7.5 (3.1)
Known Exploited
No
Published

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

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
4Source 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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2021-33950Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
n/an/an/aListed
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.