CVE-2025-43769
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.131, and Liferay DXP 2024.Q3.1 through 2024.Q3.8, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.12 and 7.4 GA through update 92 allows remote attackers to execute arbitrary web script or HTML via components tab.
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 cross-site scripting (XSS) vulnerability in Lifer Portal 7.4.0 through 7.4.3.131 and Lifer DXP multiple quarterly versions allows remote attackers to inject arbitrary web script or HTML via the components tab, which is then executed when other users view the affected components.
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.1, < 2024.Q3.9= 7.4>= 7.4.0, < 7.4.3.132CVSS 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 installed Lifer Portal versionCheck the Lifer Portal administration panel or server files for the exact version number (typically found in the Control Panel under Platform settings, or in the portal-ext.properties file)Affected if Version is 7.4.0 through 7.4.3.131 (or any 7.4.x version below 7.4.3.132)
-
Identify installed Lifer DXP versionCheck the Lifer DXP administration panel or license/version files for the quarterly version (format like 2024.Q1.x, 2024.Q2.x, 2024.Q3.x)Affected if Version matches: 2024.Q1.1 through 2024.Q1.12, 2024.Q2.0 through 2024.Q2.13, 2024.Q3.1 through 2024.Q3.8, or exactly version 7.4
-
Verify components tab accessibilityNavigate to the components tab within the Lifer interface (typically under Site Builder or Content and Data > Components) and confirm the feature is accessible to usersAffected if The components tab is present and accessible to untrusted users or external attackers
-
Inspect components for suspicious contentReview all entries in the components tab for any unexpected script tags, event handlers (onclick, onerror, onload), or HTML elements containing javascript: URIsAffected if Any component entry contains unsanitized script tags, JavaScript event handlers, or iframe/script HTML elements that were not intentionally added
-
Review server access logsExamine web server and application logs for POST requests to the components tab endpoint containing suspicious patterns like <script, javascript:, or event handler attributesAffected if Logs show requests with XSS payloads being submitted to the components functionality
A system is affected if it runs a Lifer Portal version between 7.4.0 and 7.4.3.131 inclusive, or a Lifer DXP version in any of the affected quarterly ranges, and the components tab feature is enabled and accessible to users.
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.1322024.Q1.132024.Q3.9
Update Lifer Portal/DXP to the latest patched version that addresses CVE-2025-43769. Review and sanitize user-supplied input in the components tab functionality.
Lifer Portal 7.4.3.132+ / DXP 2024.Q1.13+ / DXP 2024.Q2.14+ / DXP 2024.Q3.9+ / DXP 7.4 Update 93+
- 1. Identify the currently installed Limerick Portal or DXP version from the Control Panel > Configuration > Server Administration > Version
- 2. For Lifer Portal 7.4.x users: Upgrade to version 7.4.3.132 or later
- 3. For DXP 2024.Q1 customers: Upgrade to version 2024.Q1.13 or later
- 4. For DXP 2024.Q2 customers: Upgrade to version 2024.Q2.14 or later
- 5. For DXP 2024.Q3 customers: Upgrade to version 2024.Q3.9 or later
- 6. For DXP 7.4 subscribers: Apply update 93 or later
- 7. After upgrade, verify the components tab functionality works correctly and test that XSS payloads are no longer executable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43769 — 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-43769 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