Skip to main content
Menu
CVEs

CVE

OpenKM cross-site scripting in content parameter

Affects OpenKM v6.3.12 where the Content parameter is reflected into HTML responses without encoding. No vendor rating or fixed version is given in the checked facts.

CVE-2026-30502Published Updated Summary written by a model

8.2HighCISA-ADP
Exploited
Proof of concept public, per CISA
Fix
No fix listed
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Runs OpenKM v6.3.12 where the Content parameter is reflected into the HTML response without encoding

Summary

OpenKM contains a cross-site scripting (XSS) flaw that lets an attacker run arbitrary JavaScript in a user's browser by injecting crafted input into the Content parameter.

Original description

A Cross-Site Scripting (XSS) vulnerability in OpenKM v6.3.12 allows attackers to execute arbitrary Javascript in the context of the user's browser via a crafted input injected into the Content parameter.

Who should check

Teams running OpenKM v6.3.12 document management systems

“A Reflected Cross-Site Scripting (XSS) vulnerability was identified in OpenKM v6.3.12 via the Content parameter.”

github.com

cve.now Index

40Pcve.now Index 40 of 100 · methodology v3 · provisional
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.2/10CVSS 8.2
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active

What to do

  • Check whether your setup matches what the bug needs.

    Runs OpenKM v6.3.12 where the Content parameter is reflected into the HTML response without encoding
  • Workaround: The checked facts give no workaround or mitigation. Consult the vendor's advisory for guidance while no fix is named.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 4

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-30502
RecordNVD · CVE-2026-30502
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
ExploitGitHub · dharmstm/CVE-2026-30502-OpenKM-6.3.12-Reflected-XSS · Repository
Other links 1
RepositoryGitHub · dharmendrastm/OpenKM-6.3-Reflected-XSS-Report · Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-30502

Is CVE-2026-30502 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The Content parameter reflects input into the HTML response without encoding, so attacker-supplied JavaScript can be injected and run in the victim's browser. The script then has access to the victim's session.Source: github.com

Am I affected, and how do I check?

The checked facts name only OpenKM v6.3.12 with the Content parameter reflected without encoding. Check whether the installed OpenKM version is 6.3.12 to compare against this report.Source: github.com

How do I fix CVE-2026-30502?

The checked facts name no fixed version or vendor patch identifiers. Consult the OpenKM vendor's advisory for an update.Source: github.com

What if there's no patch?

The checked facts give no workaround or mitigation. Consult the vendor's advisory for guidance while no fix is named.Source: github.com

More CVEs