CVE-2025-43775
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 in Liferay Portal 7.4.0 through 7.4.3.128, and Liferay DXP 2024.Q3.0 through 2024.Q3.5, 2024.Q2.0 through 2024.Q2.12, 2024.Q1.1 through 2024.Q1.12, and 7.4 GA through update 92 allows remote attackers to inject arbitrary web script or HTML via remote app title 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 Limerick Portal 7.4.0-7.4.3.128 and DXP (multiple 2024.Qx versions) allows remote attackers to inject arbitrary web script or HTML via the remote app title field. The malicious payload is stored in the database and executes when other users view the remote app.
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>= 2024.Q1.1, < 2024.Q1.13>= 2024.q2.0, <= 2024.q2.13>= 2024.Q3.0, < 2024.Q3.6= 7.4>= 7.4.0, < 7.4.3.129CVSS 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 versionCheck the portal's installed version via the Control Panel or by inspecting the portal-ext.properties file or the OSGi bundle metadata. Alternatively, access the Liferium Portal administration and navigate to Configuration > Server Administration > General to view the version.Affected if The installed version falls within 7.4.0 to 7.4.3.128 for Limerick Portal, or 2024.Q1.1 to 2024.Q1.12, 2024.Q2.0 to 2024.Q2.13, or 2024.Q3.0 to 2024.Q3.5 for DXP.
-
Verify remote apps module is in useNavigate to Liferium Portal Control Panel > Apps > Remote Apps. If no remote apps have been configured, the vulnerability is not exploitable in your environment.Affected if At least one remote app is configured and the remote apps module is accessible.
-
Inspect remote app title fields for malicious contentIn the Remote Apps interface, review each remote app entry and examine the Title field for any unexpected characters, script tags, or HTML markup such as <script>, <img>, or javascript: URIs.Affected if Any remote app title contains HTML or script tags that were not intentionally added by an administrator.
-
Query database for stored XSS payloadsQuery the database table storing remote app configurations (typically RemoteAppEntry or similar) and inspect the title field for patterns like <script, onerror, javascript:, or encoded HTML entities.Affected if The database contains title values with embedded script or HTML tags that could execute in user browsers.
You are affected if your Liferium Portal/DXP version is within the affected ranges AND the remote apps feature is configured with a malicious title containing unsanitized HTML or script tags.
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.1292024.Q1.132024.Q3.6
Apply vendor-supplied patches or updates to the affected Limerick Portal/DXP versions. Until patched, restrict access to the remote app configuration interface to trusted administrators only.
2024.Q1.13 (or 2024.Q2.13, 2024.Q3.6, or 7.4.3.129 depending on version branch)
- Identify the current Liferay Portal or DXP version by checking the Control Panel > Configuration > Server Administration or examining the osgi/state/version.properties file
- Determine which version branch the current installation belongs to (2024.Q1.x, 2024.Q2.x, 2024.Q3.x, or 7.4.x)
- For 2024.Q1.x installations: Upgrade to 2024.Q1.13 or later
- For 2024.Q2.x installations: Upgrade to 2024.Q2.13 or later
- For 2024.Q3.x installations: Upgrade to 2024.Q3.6 or later
- For 7.4.x Portal installations: Upgrade to 7.4.3.129 or later
- After upgrade, verify the remote app title functionality works correctly and no XSS payloads execute
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43775 — 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-43775 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