CVE-2024-11993
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedReflected cross-site scripting (XSS) vulnerability in Liferay Portal 7.4.0 through 7.4.3.38, and Liferay DXP 7.4 GA through update 38 allows remote attackers to execute arbitrary web script or HTML via Dispatch name field
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceReflected XSS vulnerability in Lifer Portal/DXP 7.4.x allows remote attackers to inject arbitrary JavaScript/HTML through the Dispatch name field, which is reflected back without proper sanitization.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 7.1.0, < 7.4.3.39>= 7.1, < 7.4= 7.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Lifer Portal/DXP versionNavigate to Control Panel > Configuration > Server Administration > Build Information to view the installed version, or check the portal-ext.properties file for the version property, or examine the application WAR file manifestAffected if The version is 7.1.0 to 7.4.3.38 for Lifer Portal, or 7.1 to 7.4 for DXP - you are in the vulnerable range
-
Confirm Dispatch module is deployedCheck the Control Panel for the Dispatch portlet under Site Administration > Content & Data, or query the OSGi console for Dispatch-related bundlesAffected if The Dispatch module is present in the deployment
-
Verify user access to Dispatch featureCheck user roles and permissions in Control Panel > Users > Roles to see if any role grants access to the Dispatch application, or attempt to access Dispatch as a standard userAffected if Users can access the Dispatch name input field
You are affected if your Lifer version is within the vulnerable range AND the Dispatch module is enabled and accessible to users who could inject malicious script through the name field.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.47.4.3.39
Update to Lifer Portal/DXP version beyond 7.4.3.38 or apply vendor patch; implement output encoding and input validation on the Dispatch name field.
Liferay Portal 7.4.3.39+ or Liferay DXP 7.4 update 39+
- Upgrade Liferay Portal from any version >= 7.1.0 and < 7.4.3.39 to version 7.4.3.39 or later
- If using Liferay DXP 7.4 GA (any update up to 38), upgrade to DXP 7.4 update 39 or later
- After upgrade, verify the Dispatch portlet functionality works correctly and test that the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11993 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-11993 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data