NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

Cross-site Scripting in OpenCRXGHSA-96q4-7fwr-gmxh

MEDIUM

GHSA-96q4-7fwr-gmxh is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.opencrx:opencrx-core-models. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asCVE-2023-40817
Published
Updated
Affected
1 pkg
Patched
See advisory
Exploits
1 known
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-96q4-7fwr-gmxh.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk
0.00%0.32%0.64%0.96%0.1%0.5%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
☕org.opencrx:opencrx-core-models

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

OpenCRX version 5.2.0 is vulnerable to HTML injection via the Product Configuration Name Field.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
☕Mavenorg.opencrx:opencrx-core-modelsall versionsNo fix

Affected Products

1 product · 1 configurations
Application
opencrxopencrx
1 version
5.2.0
Exploits & PoCs
1

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

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Remediation status

    The records we use list no patched version of org.opencrx:opencrx-core-models for GHSA-96q4-7fwr-gmxh. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

  3. Mitigate without a patch

    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.

Frequently Asked Questions

OpenCRX version 5.2.0 is vulnerable to HTML injection via the Product Configuration Name Field.
O3 Security · Impact-Aware SCA

Is GHSA-96q4-7fwr-gmxh in your dependencies?

Find it across Maven, including transitive dependencies.

Cross-site Scripting in OpenCRX (Medium 6.1)