CVE-2025-62264
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 Languauge Override in Liferay Portal 7.4.3.8 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.10, and 7.4 update 4 through update 92 allows remote attackers to inject arbitrary web script or HTML via the `_com_liferay_portal_language_override_web_internal_portlet_PLOPortlet_selectedLanguageId` parameter.
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 Language Override feature allows remote attackers to inject arbitrary web script or HTML via the _com_lifer_portal_language_override_web_internal_portlet_PLOPortlet_selectedLanguageId parameter. The parameter is not properly sanitized before being reflected in the response, enabling script execution in victim 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.2= 2023.q3.3= 2023.q3.4= 2023.q3.5= 2023.q3.6= 2023.q3.7= 2023.q3.8= 2023.q3.9= 2023.q3.10= 2023.q4.0>= 7.4.3.8, < 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
- 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 the Lifer Portal/DXP installation versionCheck the version file in the Lifer installation directory, typically in portal-impl.jar or via the Lifer Control Panel under Configuration > Server Information. On Linux, run: find /path/to/lifer -name 'portal-impl.jar' 2>/dev/null | head -1 | xargs -I {} unzip -p {} portal-release.properties 2>/dev/null | grep 'version'Affected if The installed version is 7.4.3.8 through 7.4.3.111 (for Lifer Portal), or 7.4, or any 2023.q3.x through 2023.q3.10, or 2023.q4.0 (for Lifer DXP)
-
Confirm the Language Override portlet is enabledLog into the Lifer Control Panel as an administrator. Navigate to Configuration > Portlet Management > Portlets. Search for 'Language Override' or 'PLOPortlet'. Alternatively, check the osgi/modules directory for the language override web bundle.Affected if The Language Override portlet is installed and active on the system
-
Test for XSS via the affected parameterSend an HTTP GET request to any portal page that includes the Language Override portlet, adding the parameter _com_lifer_portal_language_override_web_internal_portlet_PLOPortlet_selectedLanguageId=<script>alert(1)</script>. For example: https://your-lifer-host/c/portal/language_override?_com_lifer_portal_language_override_web_internal_portlet_PLOPortlet_selectedLanguageId=%3Cscript%3Ealert(1)%3C/script%3E. Inspect the response HTML to see if the script tag is reflected unchanged.Affected if The script tags are returned as-is in the HTTP response without encoding or sanitization
-
Check application logs for suspicious parameter usageReview the Lifer portal access logs and Tomcat/Application server logs for requests containing the _com_lifer_portal_language_override_web_internal_portlet_PLOPortlet_selectedLanguageId parameter with unusual values.Affected if Logs show requests to this parameter with HTML or script content that was not sanitized
You are affected if the Lifer Portal/DXP version falls within the affected ranges AND the Language Override portlet is enabled, resulting in unsanitized reflection of the selectedLanguageId parameter in responses.
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.112
Apply Lifer's patched versions: Lifer Portal 7.4.3.112+, Lifer DXP 2023.Q4.11+, 2023.Q3.11+, or 7.4 update 93+. If immediate patching is not possible, disable the Language Override portlet or implement WAF rules to sanitize the affected parameter.
LPortal 7.4.3.112+ or DXP 2023.Q3.11+/2023.Q4.11+/7.4 update 93+
- 1. Identify your current Liferay DXP or LPortal version using the Control Panel > Configuration > Server Administration
- 2. For LPortal 7.4.x users: Upgrade to version 7.4.3.112 or later
- 3. For LPortal DXP 2023.Q3 users: Upgrade to 2023.Q3.11 or later
- 4. For LPortal DXP 2023.Q4 users: Upgrade to 2023.Q4.11 or later
- 5. For LPortal DXP 7.4 (update model): Upgrade to update 93 or later
- 6. After upgrade, verify the Language Override portlet no longer reflects unsanitized input in the selectedLanguageId parameter
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-62264 — 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-62264 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