CVE-2024-25152
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 · uneditedStored cross-site scripting (XSS) vulnerability in Message Board widget in Liferay Portal 7.2.0 through 7.4.2, and older unsupported versions, and Liferay DXP 7.3 before service pack 3, 7.2 before fix pack 17, and older unsupported versions allows remote authenticated users to inject arbitrary web script or HTML via the filename of an attachment.
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 confidenceStored cross-site scripting (XSS) vulnerability in Liferay Portal and DXP's Message Board widget allows authenticated users to inject malicious web script or HTML via the filename of an attachment. The malicious payload persists and executes when other users view the attachment.
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.4.3.4< 7.2= 7.2= 7.3CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Check LPortal or DXP versionLocate the version file in the Liferay installation directory (typically in the tomcat/webapps/ROOT/WEB-INF/classes/portal-ext.properties or via the Control Panel > Configuration > Server Administration > Version). Compare against affected ranges: Portal < 7.4.3.4, DXP < 7.2, DXP = 7.2, DXP = 7.3.Affected if The installed version falls within the affected ranges listed above.
-
Verify Message Board widget is in useAccess the Liferaray Control Panel and navigate to Site Administration > Content & Data > Message Boards, or check if the Message Board portlet is deployed on any page via the Pages and Portlets administration panel.Affected if The Message Board widget is active or has been used within the environment.
-
Inspect Message Board attachmentsQuery the database for entries in the MBMessage table (or equivalent) where the attachments column contains records. Alternatively, navigate through the Message Board UI to view threads with attachments and note the filename field for each attachment.Affected if There exist Message Board posts with file attachments present in the system.
-
Review attachment filenames for unsanitized inputExamine the filename values of Message Board attachments directly in the database (typically stored in the Attachment table or MBAttachment table) or via the UI. Look for filenames containing HTML tags, script elements, or JavaScript event handlers (e.g., <script>, onerror=, onload=, img src=).Affected if Any attachment filename contains raw HTML or script syntax without sanitization.
You are affected if you run an affected LPortal/DXP version AND have the Message Board widget with attachments enabled, as the vulnerability allows authenticated users to store unsanitized filenames that execute XSS when viewed by others.
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.27.4.3.4
Apply vendor patches: Liferay Portal 7.4.3+, DXP 7.3 Service Pack 3+, or DXP 7.2 Fix Pack 17+. Alternatively, implement strict input validation and sanitization on attachment filenames before storage.
Liferay Portal 7.4.3.4+ / DXP 7.3 SP3+ / DXP 7.2 FP17+
- 1. Identify the current Liferay Portal or DXP version currently installed
- 2. For Liferay Portal users: Upgrade to version 7.4.3.4 or later
- 3. For Liferay DXP 7.3 users: Upgrade to service pack 3 or later
- 4. For Liferay DXP 7.2 users: Apply fix pack 17 or later
- 5. After upgrade, verify the Message Board widget attachment functionality works correctly
- 6. Test that the XSS vulnerability is no longer exploitable via attachment filenames
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-25152 — 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-25152 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