CVE-2025-62238
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 on the Membership page in Account Settings in Liferay Portal 7.4.3.21 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.8, and 7.4 update 21 through update 92 allows remote authenticated attackers to inject arbitrary web script or HTML via a crafted payload injected into a Account's “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 · moderate confidenceStored cross-site scripting (XSS) vulnerability in Liferay Portal and DXP allows authenticated attackers to inject malicious JavaScript/HTML into the Account Name field on the Membership page. The payload persists and executes when other users view the affected page, enabling session hijacking or defacement.
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.9>= 2023.q4.0, < 2023.q4.6= 7.4>= 7.4.3.21, < 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 Liferax Portal or DXP versionCheck the portal version in the Control Panel under Configuration > Server Administration, or inspect the portal-ext.properties file for the version property, or review the bundle's liferay-portal/tomcat logs at startup showing the version numberAffected if The installed version falls within 7.4.3.21 through 7.4.3.111 for LXP Portal; or 2023.q3.1 through 2023.q3.8, 2023.q4.0 through 2023.q4.5, or exactly 7.4 for DXP
-
Verify Account Management feature is in useNavigate to Control Panel > Users > Accounts, or access the Accounts module via the URL /group/accounts, and confirm that any account records exist in the systemAffected if Accounts have been created and the Account Management interface is accessible to authenticated users
-
Inspect stored Account Name values for suspicious contentQuery the Account_ table in the Liferay database, or export accounts via the API endpoint /o/c/accounts, and examine the name field for HTML tags, script elements, or JavaScript event handlers such as onload, onerror, or onclickAffected if Any account name contains unencoded HTML markup, script tags, or javascript: URIs, indicating potential XSS payload injection
-
Check Membership page accessibilityNavigate to an account's Memberships tab (typically at /group/accounts/{accountId}/memberships) as an authenticated user and verify the Account Name field is displayed and editableAffected if The Membership page renders account names without output encoding, allowing stored XSS to execute when viewed by other users
You are affected if your Liferay version is within the affected ranges AND the Account Management feature is actively used, with any account names containing unsanitized HTML or script content that would execute when the Membership page is viewed.
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
Apply the vendor patch or upgrade to a version beyond Liferay Portal 7.4.3.111 and DXP 2023.Q4.5 (including all 7.4 updates beyond update 92). Implement output encoding on the Account Name field as an additional defense-in-depth measure.
Lifer Portal 7.4.3.112, or Lifer DXP 2023.Q3.9, or Lifer DXP 2023.Q4.6, or Lifer DXP 7.4 update 93+
- 1. Identify the exact current Lifer DXP/Portal version and update number by checking the Lifer Tomcat bundle or portal-ext.properties
- 2. Review the Lifer DXP/Portal 7.4 compatibility matrix and release notes for the target fixed version
- 3. Create a full backup of the database and Lifer bundle (documents, configuration files)
- 4. In a non-production environment (dev/staging), apply the upgrade: For Lifer Portal 7.4.x, upgrade to 7.4.3.112; For Lifer DXP 2023.Q3.x, upgrade to 2023.Q3.9; For Lifer DXP 2023.Q4.x, upgrade to 2023.Q4.6; For Lifer DXP 7.4 update versions, upgrade to update 93 or later
- 5. Run the Lifer database migration scripts and verify successful upgrade via Gogo shell or admin console
- 6. Test the Account Settings Membership page functionality to confirm the fix works and no regressions exist
- 7. Apply the same upgrade to production environment after successful validation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62238 — 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-62238 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