CVE-2025-62246
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 stored cross-site scripting (XSS) vulnerabilities in Liferay Portal 7.4.0 through 7.4.3.111, and older unsupported versions, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.8, 7.4 GA through update 92, and older unsupported versions allow remote authenticated users to inject arbitrary web script or HTML via a crafted payload injected into a user’s first, middle or last name text field to (1) page comments widget, (2) blog entry comments, (3) document and media document comments, (4) message board messages, (5) wiki page comments or (6) other widgets/apps that supports mentions.
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 XSS vulnerability in Limerick Portal/DXP where authenticated users can inject malicious JavaScript/HTML into their profile name fields (first, middle, last name). When these user names are displayed in comments (page, blog, document, message board, wiki) or widgets supporting mentions, the injected payload executes in victims' browsers.
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>= 2023.q3.1, < 2023.q3.9>= 2023.q4.0, < 2023.q4.6>= 7.1.0, < 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 Limerick Portal/DXP versionCheck the installed version via the control panel (Control Panel > Configuration > System Information) or inspect the portal-ext.properties file for version properties, or look at the WAR file timestamp/nameAffected if Version matches: DXP <= 7.4, DXP 2023.q3.1-2023.q3.8, DXP 2023.q4.0-2023.q4.5, or Portal 7.1.0-7.4.3.111
-
Verify user profile name fields existNavigate to My Account or Control Panel > Users > Users and Personal Settings, locate the profile name fields (first name, middle name, last name)Affected if The application has user profile name fields that can be edited by authenticated users
-
Confirm comment or mention features are enabledCheck if any of these are active: Message Boards, Blogs, Documents and Media comments, Wiki, or widgets that support @mentions. Inspect Site Administration > Content & Data or check portal-ext.properties for com_liferaysite_comment_* enablement flagsAffected if Any comment system (page comments, blog comments, document comments, message board, wiki) or mention-capable widgets are enabled and accessible to users
-
Inspect existing user profile names for malicious payloadsQuery the User_ table in the database for user names containing script tags, javascript:, onload, onerror, or other XSS vectors. Example SQL: SELECT userId, firstName, middleName, lastName FROM User_ WHERE firstName LIKE '%<script%' OR middleName LIKE '%onerror%' OR lastName LIKE '%javascript:%'Affected if Any user records contain suspicious patterns in name fields that could be XSS payloads
You are affected if your Limerick version falls within the affected ranges AND authenticated users can edit their profile names AND any comment or mention feature that displays those names is enabled, especially if malicious payloads are already present in user name fields.
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.92023.q4.6
Upgrade to latest Limerick version with security patch, or implement input validation and output encoding on user profile name fields and all affected comment rendering contexts.
LPortal 7.4.3.112 or DXP 2023.Q3.9 or DXP 2023.Q4.6 or DXP 7.4 GA update 93
- Review the current LPortal/DXP version using the Server Administration panel or platform configuration
- Create a complete backup of the database and Liferay home directory including deployed plugins and configuration files
- Download the appropriate fixed release based on current version: LPortal 7.4.3.112+ or DXP 2023.Q3.9+ or DXP 2023.Q4.6+ or DXP 7.4 GA update 93+
- Stop the LPortal/DXP application server services
- Deploy the new Liferay WAR file and required JAR files following the official upgrade documentation
- Run the database upgrade tool to migrate schema if required
- Update any custom plugins or themes to be compatible with the target version
- Start the application server and verify all services start successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62246 — 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-62246 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