CVE-2025-43807
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 the notifications widget in Liferay Portal 7.4.0 through 7.4.3.112, and Liferay DXP 2023.Q4.0 through 2023.Q4.8, 2023.Q3.1 through 2023.Q3.10, and 7.4 GA through update 92 allows remote attackers to inject arbitrary web script or HTML via a crafted payload injected into a publication’s “Name” text 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 · high confidenceStored XSS vulnerability in Lifer DXP/Portal notifications widget allows attackers to inject malicious scripts via the publication 'Name' field. The injected payload persists in the database and executes when other users view the notifications widget.
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.1, <= 2023.Q3.10>= 2023.Q4.0, < 2023.Q4.9= 7.4>= 7.4.0, < 7.4.3.113CVSS 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 installed Lifer versionAccess the Lifer Server Diagnostics page (typically at /group/control_panel/manage?p_p_id=com_liferay_server_admin_web_portlet_ServerAdminPortlet) or check the Lifer bundle version information in the OSGi console. Alternatively, check the liferay-relative-url.properties or portal-version.properties files in the Lifer installation directory.Affected if The version falls within 2023.Q3.1 to 2023.Q3.10, 2023.Q4.0 to less than 2023.Q4.9, 7.4, or 7.4.0 to less than 7.4.3.113
-
Determine if Publications feature is enabledNavigate to Lifer Control Panel > Configuration > Publications, or query the database table Lifer_Publication (if direct database access is available) to check for active publication records.Affected if Publications feature is enabled and has publications configured with a Name field
-
Verify if notifications widget is accessible to usersNavigate to the site pages where the Notifications widget may be added (typically found in the User Dashboard, My Sites, or customizable site pages). Check the widget configuration via the Lifer UI or examine the portlet preferences in the database table LayoutPortletPrefs.Affected if The Notifications widget is present and visible to users on any page accessible to other users
-
Inspect publication names in databaseQuery the Lifer_Publication table (or equivalent) for any publication records. Examine the name column for potential XSS payloads by reviewing data patterns or using database inspection tools.Affected if The publication name field contains unsanitized HTML or script content (this indicates active exploitation)
A user is affected if they are running a Lifer version within the affected ranges AND the Publications feature is in use, allowing the stored XSS in the notification widget to execute when users view the notifications.
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.1132023.Q4.9
Upgrade to a patched Lifer version beyond the affected releases. Additionally, implement proper input validation and output encoding on the Name field as a defense-in-depth measure.
Lifer DXP 2023.Q4.9+ or Lifer DXP/Portal 7.4.3.113+
- 1. Back up your current Liferay database and deployment configuration
- 2. Identify your current Lifer DXP or Portal version using the Admin Panel or version properties
- 3. If running Lifer DXP 2023.Q4.0 through 2023.Q4.8, upgrade to Lifer DXP 2023.Q4.9 or later
- 4. If running Lifer DXP 7.4 GA through update 92, upgrade to Lifer DXP 7.4.3.113 or later
- 5. If running Lifer Portal 7.4.0 through 7.4.3.112, upgrade to Lifer Portal 7.4.3.113 or later
- 6. Verify the upgrade was successful by checking the Lifer version in the Control Panel > Configuration > System Information
- 7. Test the notifications widget to confirm the XSS fix is applied and the Name field now sanitizes input properly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43807 — 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-43807 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