CVE-2025-43740
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 · uneditedA Stored cross-site scripting vulnerability in the Liferay Portal 7.4.3.120 through 7.4.3.132, and Liferay DXP 2025.Q2.0 through 2025.Q2.8, 2025.Q1.0 through 2025.Q1.15, 2024.Q4.0 through 2024.Q4.7, 2024.Q3.1 through 2024.Q3.13, 2024.Q2.1 through 2024.Q2.13 and 2024.Q1.9 through 2024.Q1.19 allows an remote authenticated attacker to inject JavaScript through the message boards feature available via the web interface.
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 confidenceA stored cross-site scripting (XSS) vulnerability in Liferay Portal and DXP's message boards feature allows an authenticated remote attacker to inject malicious JavaScript that persists and executes when other users view the infected message boards content.
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.9, < 2024.Q1.20>= 2024.Q2.1, <= 2024.Q2.13>= 2024.q3.1, <= 2024.q3.13>= 2024.q4.0, <= 2024.q4.7>= 2025.Q1.0, < 2025.Q1.16>= 2025.Q2.0, < 2025.Q2.9>= 7.4.3.120, <= 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
- 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 Lifer DXP or Portal versionAccess the Lifer Control Panel, go to Configuration > Server Administration > Product Information, or check the portal-ext.properties file for the version propertyAffected if The installed version falls within any of these ranges: 2024.Q1.9 to 2024.Q1.19; 2024.Q2.1 to 2024.Q2.13; 2024.q3.1 to 2024.q3.13; 2024.q4.0 to 2024.q4.7; 2025.Q1.0 to 2025.Q1.15; 2025.Q2.0 to 2025.Q2.8 (for DXP) or 7.4.3.120 to 7.4.3.132 (for Portal)
-
Confirm Message Boards module is enabledNavigate to Control Panel > Apps > App Manager, or check the OSGi console for the com.lifer.message.boards module bundle statusAffected if The Message Boards component is active and installed on the system
-
Verify Message Boards permissions allow user postingGo to Control Panel > Users > Roles, check if authenticated users or non-admin roles have Message Boards permission to create or reply to threadsAffected if Regular authenticated users can post to message boards without admin oversight
-
Inspect existing Message Boards content for XSS payloadsAccess the Message Boards portlet via the site administration, review recent thread titles and posts for unusual script tags, event handlers, or encoded charactersAffected if Any message board thread contains unrecognized script tags, javascript: URIs, or HTML event attributes like onload, onerror, or onclick
A system is affected if it runs a Lifer DXP or Portal version within the specified ranges AND has the Message Boards feature enabled with posting permissions for authenticated 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 · scoped2024.Q1.202025.Q1.162025.Q2.9
Upgrade to Liferay 7.4.3.133 or later, or apply the relevant security patch for affected DXP versions; implement input validation and output encoding on message board content as a compensating control.
Lifteray Portal 7.4.3.133+ or DXP 2024.Q1.20+/2024.Q2.14+/2024.Q3.14+/2024.Q4.8+/2025.Q1.16+/2025.Q2.9+ depending on your product line
- 1. Identify your current Lifteray installation version from the Control Panel > Configuration > Server Administration > Product Information.
- 2. For Liferay Portal 7.4.3.x users: Upgrade to version 7.4.3.133 or later.
- 3. For Liferav Digital Experience Platform 2024.Q1 users: Upgrade to version 2024.Q1.20 or later.
- 4. For DXP 2024.Q2 users: Upgrade to version 2024.Q2.14 or later.
- 5. For DXP 2024.Q3 users: Upgrade to version 2024.Q3.14 or later.
- 6. For DXP 2024.Q4 users: Upgrade to version 2024.Q4.8 or later.
- 7. For DXP 2025.Q1 users: Upgrade to version 2025.Q1.16 or later.
- 8. For DXP 2025.Q2 users: Upgrade to version 2025.Q2.9 or later.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.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 $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43740 — 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-43740 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