dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43818

MEDIUM · 6.1 CVSS v3.1 Published 2025-09-29
Fix available
A fix is available. Upgrade to 7.4.3.111 / 2023.Q3.7 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Cross-site scripting (XSS) vulnerability in the Calendar widget in Liferay Portal 7.4.3.35 through 7.4.3.110, and Liferay DXP 2023.Q4.0 through 2023.Q4.4, 2023.Q3.1 through 2023.Q3.6, 7.4 update 35 through update 92, and 7.3 update 25 through update 36 allows remote attackers to inject arbitrary web script or HTML via a crafted payload injected into a Calendar'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 confidence

A stored Cross-Site Scripting (XSS) vulnerability exists in the Calendar widget of Liferay Portal and DXP. Attackers can inject malicious JavaScript or HTML into the Calendar's 'Name' field, which then executes when other users view or interact with the calendar entry.

MitigationUpdate Liferay Portal/DXP to a patched version beyond the affected version ranges. Apply input validation and output encoding to the Calendar widget Name field to prevent XSS.

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
Digital Experience PlatformApplication
Affected:>= 2023.Q3.1, < 2023.Q3.7>= 2023.Q4.0, < 2023.Q4.5= 7.3= 7.4
Liferay PortalApplication
Affected:>= 7.4.3.35, < 7.4.3.111

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify L Portal/DXP version
    Access the L Control Panel > Configuration > Server Information, or check the osgi/state/org.apache.felix.framework-*.properties file in the L installation directory, or query the L API endpoint /api/jsonws/license/get-current-build-info
    Affected if The version falls within >= 2023.Q3.1 and < 2023.Q3.7, or >= 2023.Q4.0 and < 2023.Q4.5, or equals 7.3 or 7.4 for DXP; or >= 7.4.3.35 and < 7.4.3.111 for Portal
  2. Confirm Calendar widget is active
    Navigate to Site Administration > Site Builder > Pages, or check the L database table layout for pages containing portlet ID com_lifercalendar_portlet_CalendarPortlet, or inspect the OSGi console for com_lifercalendar bundle
    Affected if The Calendar widget is deployed and active on any site or page within the instance
  3. Check Calendar Name field is accessible to users
    Navigate to the Calendar widget UI, click Add Event or Create Calendar, locate the Name field, or query the L database table calendar_calendar for entries with non-null name fields
    Affected if Users with contributor-level or higher permissions can access the Calendar Name input field
  4. Inspect Calendar entries for malicious scripts
    Query the calendar_calendar table in the L database for Name field values containing script tags, html tags, or javascript: URIs; or manually review Calendar entries through the UI for unusual characters in the Name field
    Affected if Any Calendar Name entry contains encoded or raw HTML/JavaScript like <script>, javascript:, or event handlers such as onload/onerror

The environment is affected if running a vulnerable L version AND the Calendar widget is accessible to users who can create or edit calendar entries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.4.3.111 / 2023.Q3.7 / 2023.Q4.5 or later
Fixed in 7.4.3.1112023.Q3.72023.Q4.5
Interim mitigation

Update Liferay Portal/DXP to a patched version beyond the affected version ranges. Apply input validation and output encoding to the Calendar widget Name field to prevent XSS.

Recommended fix High confidence

Upgrade to 2023.Q3.7, 2023.Q4.5, or 7.4.3.111 (or later) depending on your product line; for DXP 7.3/7.4 contact Lifer support for the specific fixed update

  1. 1. Identify the current Lifer Portal/DXP version by navigating to Control Panel > Configuration > Server Administration > Version
  2. 2. For DXP 2023.Q3.x instances: Plan upgrade to version 2023.Q3.7 or later
  3. 3. For DXP 2023.Q4.x instances: Plan upgrade to version 2023.Q4.5 or later
  4. 4. For Lifer Portal 7.4.3.x instances (where x >= 35): Plan upgrade to version 7.4.3.111 or later
  5. 5. For DXP 7.4 instances: Upgrade to the latest available update pack that includes the fix (update 93 or later)
  6. 6. For DXP 7.3 instances: Contact Lifer support for the specific fixed update pack
  7. 7. Before production deployment, test the upgrade in a staging environment to verify the Calendar widget functions correctly
  8. 8. After upgrade, verify the fix by attempting to create a Calendar with a malicious script in the Name field - it should be sanitized and not execute
Caveat Minor: Review release notes for any deprecations or behavioral changes between your current version and the target upgrade version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43818 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-43818 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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