How severe is GHSA-c8j6-gqq8-4prj?

No CVSS score has been assigned to GHSA-c8j6-gqq8-4prj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-c8j6-gqq8-4prj?

GHSA-c8j6-gqq8-4prj affects the following packages: org.opencms:opencms-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-c8j6-gqq8-4prj?

Update org.opencms:opencms-core to 11.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c8j6-gqq8-4prj is resolved across your whole dependency graph.

How do I detect GHSA-c8j6-gqq8-4prj in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opencms:opencms-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-c8j6-gqq8-4prj if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-c8j6-gqq8-4prj actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-c8j6-gqq8-4prj, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-c8j6-gqq8-4prj?

GHSA-c8j6-gqq8-4prj has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 55th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-c8j6-gqq8-4prj?

GHSA-c8j6-gqq8-4prj is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-c8j6-gqq8-4prj published, and has it been updated?

GHSA-c8j6-gqq8-4prj was published on May 24, 2022 and was last updated on June 20, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

Alkacon OpenCMS XSS via New User moduleGHSA-c8j6-gqq8-4prj

Fix: alkacon/opencms-core@b20c293

GHSA-c8j6-gqq8-4prj is a Cross-site Scripting (XSS) vulnerability in org.opencms:opencms-core. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.opencms:opencms-core — see the affected versions and patch details below.

Also known asCVE-2019-11818

Published

May 24, 2022

Updated

Jun 20, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.opencms:opencms-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Alkacon OpenCMS v10.5.4 and before is affected by stored cross site scripting (XSS) in the module New User (/opencms/system/workplace/admin/accounts/user_new.jsp). This allows an attacker to insert arbitrary JavaScript as user input (First Name or Last Name), which will be executed whenever the affected snippet is loaded.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.opencms:opencms-core`	all versions	11.0.0`org.opencms:opencms-core:11.0.0`

Affected Products

1 product · 1 configurations

Application

opencmsalkacon

≤ 10.5.4

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Alkacon OpenCMS v10.5.4 and before is affected by stored cross site scri…

openwall.comNVDMay 2019

Report on github.com

github.comNVDMay 2019

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opencms:opencms-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.opencms:opencms-core to 11.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c8j6-gqq8-4prj is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.