CVE-2023-27150 json
OpenCRX Cross-site Scripting vulnerability
published 2y ago modified 4mo ago also GHSA-8wjx-p2f8-5rjp , EUVD-2023-3166
- cvss
- 5.4
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 34%
- public exploits
- 0
- none known
Summary
openCRX 5.2.0 was discovered to contain a cross-site scripting (XSS) vulnerability via the Name field after creation of a Tracker in Manage Activity.
Is CVE-2023-27150 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-15).
Exploits and checks
- esecforte.com https://www.esecforte.com/cve-2023-27150-cross-site-scripting-xss/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| GitHub | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.opencrx:opencrx-core | <=5.2.0 |
no fix listed |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
esecforte.com
/cve-2023-27150-cross-site-scripting-xss/
exploit, third-party-advisory
-
opencrx.org
/
product
-
nvd.nist.gov
/vuln/detail/CVE-2023-27150
advisory
-
github.com
/opencrx/opencrx
package
-
esecforte.com
/cve-2023-27150-cross-site-scripting-xss
web
-
opencrx.org
web
Sources
- CVE List CVE-2023-27150
- GitHub Advisory GHSA-8wjx-p2f8-5rjp
- NVD CVE-2023-27150
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.