CVE-2023-33725 json
Broadleaf vulnerable to Cross-site Scripting
published 2023-06-21 3 y ago modified 2026-06-17 4 mo ago also GHSA-3862-fmr3-4f3h , EUVD-2023-1667
- cvss
- 6.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
Broadleaf 5.x and 6.x (including 5.2.25-GA and 6.2.6-GA) was discovered to contain a cross-site scripting (XSS) vulnerability via a customer signup with a crafted email address. This is fixed in 6.2.6.1-GA.
Patch / fix
- maven org.broadleafcommerce:broadleaf 6.2.7-GA
- broadleafcommerce broadleaf_commerce 6.2.6.1-ga
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 23 mo ago
Exploit prediction
0.50% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/Contrast-Security-OSS/Burptrast/tree/main/docs/CVE-2023-33725 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| CNA | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| GitHub | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.broadleafcommerce:broadleaf | >=5.0.0-GA, <6.2.7-GA |
6.2.7-GA |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/Contrast-Security-OSS/Burptrast/tree/main/docs/CVE-2023-33725
web, exploit, mitigation, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-33725
advisory
-
github.com
/BroadleafCommerce/BroadleafCommerce
package
Sources
- CVE List CVE-2023-33725
- GitHub Advisory GHSA-3862-fmr3-4f3h
- NVD CVE-2023-33725
Fencer Vulns 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.