CVE-2025-62240
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 · uneditedMultiple cross-site scripting (XSS) vulnerabilities with Calendar events in Liferay Portal 7.4.3.35 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.7, 7.4 update 35 through update 92, and 7.3 update 25 through update 36 allow remote attackers to inject arbitrary web script or HTML via a crafted payload injected into a user’s (1) First Name, (2) Middle Name or (3) Last Name text 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 confidenceMultiple stored XSS vulnerabilities in Lifieri Portal and DXP allow attackers to inject arbitrary web script or HTML via crafted payloads in user profile fields (First Name, Middle Name, Last Name) that are displayed in Calendar events. The vulnerability stems from insufficient input sanitization when user profile data is rendered in the Calendar component.
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>= 2023.Q3.1, < 2023.Q3.8>= 2023.q4.0, < 2023.q4.6= 7.3= 7.4>= 7.4.3.35, < 7.4.3.112CVSS 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.
-
Identify Liferi product and versionLocate the installed Liferi Portal or DXP version through the control panel (Control Panel > Configuration > System Information) or check the portal-ext.properties file for the version numberAffected if The installed version falls within any of these ranges: DXP 2023.Q3.1 through 2023.Q3.7, DXP 2023.Q4.0 through 2023.Q4.5, DXP 7.3, DXP 7.4, or Portal 7.4.3.35 through 7.4.3.111
-
Verify Calendar module is activeCheck if the Calendar application is deployed and accessible in the Liferi instance through the app manager or by attempting to access the Calendar portletAffected if The Calendar feature is enabled and users can view calendar events that display user profile information
-
Examine user profile field storageQuery the User_ table in the Liferi database, specifically the firstName, middleName, and lastName columns, or inspect user profile data through the Liferi control panelAffected if Any user accounts contain HTML or JavaScript characters (such as <script>, javascript:, onload, onerror) in the First Name, Middle Name, or Last Name fields
-
Review Calendar event renderingCreate a test calendar event or view existing events and inspect the page source to see if user profile names are being rendered with proper encodingAffected if User names from profile fields are displayed in Calendar events without HTML entity encoding (e.g., raw <script> tags appear in the page source)
-
Check for existing XSS indicatorsSearch web server logs and Liferi database for any suspicious patterns in user profile fields, such as encoded or raw script tags in name fieldsAffected if Malicious payloads are found stored in user profile name fields
A user is affected if the Liferi version matches the vulnerable ranges AND the Calendar component is active, allowing stored XSS via unescaped user profile name fields rendered in calendar events.
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.4.3.1122023.Q3.82023.q4.6
Upgrade Lifieri Portal to version 7.4.3.112 or later, and upgrade affected DXP versions to their respective fixed releases (2023.Q4.6+, 2023.Q3.8+, etc.). Alternatively, implement input validation and output encoding for user profile fields at the application layer until patches can be applied.
Lifer Portal: 7.4.3.112+ | DXP: 2023.Q3.8+, 2023.Q4.6+, or later update versions
- 1. Identify the currently deployed Lifter Portal or DXP version using the Control Panel or administration console.
- 2. For Lifer Portal 7.4.x users: Plan an upgrade to version 7.4.3.112 or later.
- 3. For DXP 2023.Q3.x users: Plan an upgrade to version 2023.Q3.8 or later.
- 4. For DXP 2023.Q4.x users: Plan an upgrade to version 2023.Q4.6 or later.
- 5. For DXP 7.3 and 7.4 users: Upgrade to the corresponding later updates that include the security fix.
- 6. Before upgrading in production, test the upgrade in a staging environment to verify compatibility with existing customizations and data.
- 7. Perform a full backup of the database and filesystem before applying the upgrade.
- 8. Apply the upgrade following Lifer's standard upgrade documentation and restart the server.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62240 — 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-2025-62240 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