Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-vwjx-mmwm-pwrf

CRITICAL

GHSA-vwjx-mmwm-pwrf is a critical-severity (CVSS 10) XML External Entity (XXE) vulnerability in org.lucee:lucee. O3 Security confirms whether GHSA-vwjx-mmwm-pwrf is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Lucee RCE/XXE Vulnerability

Also known asCVE-2023-38693
Published
Mar 5, 2025
Updated
Mar 5, 2025
Affected
5 pkgs
Patched
4 / 5
Exploits
None indexed

Blast Radius

5 pkgs affected
org.lucee:luceeorg.lucee:luceeorg.lucee:luceeorg.lucee:luceeorg.lucee:lucee

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

Impact

The Lucee team received a responsible disclosure of a security vulnerability which affects all previous releases of Lucee.

After reviewing the report and confirming the vulnerability, the Lucee team then conducted a further security review and found additional vulnerabilities which have been addressed as part of this this security update.

Patches

Lucee 5.4.3.2 and 5.3.12.1 stable releases have been patched with additional hardening

The older releases, 5.3.7.59., 5.3.8.236 and 5.3.9.173 have also been patched

Any users running older release, should plan to immediately upgrade to the latest stable release

6.0 will have a RC as it's not yet released

Affected Packages

5 total 4 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.lucee:lucee5.3.10.79-RC&&< 5.3.12.15.3.12.1
Mavenorg.lucee:lucee5.4.0.65-RC&&< 5.4.3.25.4.3.2
Mavenorg.lucee:luceeall versionsNo fix
Mavenorg.lucee:lucee5.3.8.132-RC&&< 5.3.8.2365.3.8.236
Mavenorg.lucee:lucee5.3.9.113&&< 5.3.9.1735.3.9.173

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.lucee:lucee. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.lucee:lucee to 5.3.12.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vwjx-mmwm-pwrf is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-vwjx-mmwm-pwrf is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-vwjx-mmwm-pwrf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact The Lucee team received a responsible disclosure of a security vulnerability which affects all previous releases of Lucee. After reviewing the report and confirming the vulnerability, the Lucee team then conducted a further security review and found additional vulnerabilities which have been addressed as part of this this security update. ### Patches Lucee 5.4.3.2 and 5.3.12.1 stable releases have been patched with additional hardening The older releases, 5.3.7.59., 5.3.8.236 and 5.3.9.173 have also been patched Any users running older release, should plan to immediately upgra
O3 Security · Impact-Aware SCA

Is GHSA-vwjx-mmwm-pwrf in your dependencies?

O3 detects GHSA-vwjx-mmwm-pwrf across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.