Skip to main content
CVE-2023-50072VulnerabilityPublished Updated

CVE-2023-50072: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 5.4 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Jan 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
GitHubahrixia/OpenKMpkg:github/ahrixia/OpenKMOther threatsAffected
  • =7.1.40
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should implement the following specific mitigations: 1) Restrict note upload permissions strictly to trusted and trained users to reduce the risk of malicious payload insertion. 2) Implement input validation and output encoding on note content to neutralize any embedded scripts before storage or rendering. 3) Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in the browser context. 4) Monitor and audit user activities related to document notes for unusual or suspicious behavior. 5) Educate users to be cautious when opening notes, especially from less trusted sources. 6) If possible, upgrade to a newer OpenKM version where this vulnerability is fixed or apply vendor-provided patches once available. 7) Use web application firewalls (WAFs) with rules targeting XSS payload patterns to provide an additional layer of defense. 8) Regularly review and update authentication and session management controls to minimize the impact of session hijacking attempts.

Description

A Stored Cross-Site Scripting (XSS) vulnerability exists in OpenKM version 7.1.40 (dbb6e88) With Professional Extension that allows an authenticated user to upload a note on a file which acts as a stored XSS payload. Any user who opens the note of a document file will trigger the XSS.

References

Community reviews

Loading reviews…