CVE-2025-43804
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 · uneditedCross-site scripting (XSS) vulnerability in Search widget in Liferay Portal 7.4.3.93 through 7.4.3.111, and Liferay DXP 2023.Q4.0, 2023.Q3.1 through 2023.Q3.4 allows remote attackers to inject arbitrary web script or HTML via the _com_liferay_portal_search_web_portlet_SearchPortlet_userId 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 confidenceCross-site scripting (XSS) vulnerability in the Search widget of Liferay Portal 7.4.3.93-7.4.3.111 and Limerick DXP 2023.Q4.0/2023.Q3.x allows remote attackers to inject arbitrary web script or HTML via the _com_lirebase_portal_search_web_portlet_SearchPortlet_userId parameter. The userId parameter is not properly sanitized before being reflected in the HTML output.
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.0= 2023.q3.1= 2023.q3.2= 2023.q3.3= 2023.q3.4= 2023.q4.0= 2023.q4.1>= 7.4.3.93, < 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 Limerick DXP or Portal versionAccess the Liferay Control Panel > Configuration > Server Administration > Product Menu, or check the bundle version in the OSGi console using 'version' command, or inspect the portal-ext.properties file for version information.Affected if The installed version is 2023.q3.0 through 2023.q4.1 for Limerick DXP, or 7.4.3.93 through 7.4.3.111 for Portal.
-
Confirm SearchPortlet module is deployedCheck for the presence of the SearchPortlet in the deployed web applications or OSGi modules. In the Liferay control panel, navigate to Apps > App Manager, or query the OSGi console for 'com_lirebase_portal_search_web_portlet_SearchPortlet'.Affected if The SearchPortlet module is installed and active in the Limerick DXP 2023.Q3.x/2023.Q4.x or Portal 7.4.3.93-7.4.3.111 environment.
-
Verify userId parameter handling in SearchPortletInspect the SearchPortlet JSP or Java source files for the userId parameter handling. Look for code that retrieves the _com_lirebase_portal_search_web_portlet_SearchPortlet_userId parameter without output encoding. In a deployed environment, decompile or inspect the portal-search-web-portlet JAR for the SearchPortlet class.Affected if The SearchPortlet code reflects the userId parameter directly into HTML without proper sanitization (no HTML encoding or input validation present).
-
Test for XSS via userId parameterIf you have access to the SearchPortlet interface, submit a search request with a crafted userId parameter value such as '<script>alert(1)</script>' in the URL query string using the parameter _com_lirebase_portal_search_web_portlet_SearchPortlet_userId. Observe if the value is reflected unescaped in the response.Affected if The malicious script payload is executed or rendered unescaped in the browser, confirming the XSS vulnerability exists in the SearchPortlet.
You are affected if your Limerick DXP version is 2023.Q3.0 through 2023.Q4.1 (or Portal version 7.4.3.93 through 7.4.3.111), the SearchPortlet is active, and the userId parameter is reflected without HTML encoding.
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
Update to Limerick DXP 2023.Q4.1 or later / Portal 7.4.3.112 or later. Alternatively, implement input validation and output encoding for the userId parameter in the SearchPortlet to neutralize malicious script injection.
LPortal: 7.4.3.112 or later; DXP: 2023.Q4.0 or later
- 1. Identify the exact LPortal or DXP version currently running in your environment.
- 2. For LPortal users: Upgrade to LPortal 7.4.3.112 or later, which contains the fix for this XSS vulnerability in the Search widget.
- 3. For DXP users: Upgrade to DXP 2023.Q4.0 or later, which contains the fix.
- 4. After upgrading, verify the Search widget functions correctly and that the _com_lifera_poral_search_web_portlet_SearchPortlet_userId parameter is properly sanitized.
- 5. Test that existing Search widget configurations and customizations remain functional after the upgrade.
- 6. Consider reviewing other widgets and parameters for similar XSS issues as a precautionary measure.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43804 — 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-43804 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