CVE-2025-43820
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 · uneditedMultiple cross-site scripting (XSS) vulnerabilities in the Calendar widget when inviting users to a event 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 35 allow remote attackers to inject arbitrary web script or HTML via a crafted payload injected into a user’s (1) First Name, (2) Middle text, or (3) Last Name text fields.
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 LPortal's Calendar widget where user profile fields (First Name, Middle Name, Last Name) are not sanitized when displaying invited event attendees, allowing injected JavaScript/HTML to execute in victims' browsers.
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.7>= 2023.Q4.0, < 2023.Q4.5= 7.3= 7.4>= 7.4.3.35, < 7.4.3.111CVSS 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.
-
Determine LPortal/Liferay versionAccess the Control Panel > Configuration > Server Administration > Global Preferences, or check the bundle properties file (portal-impl.properties or portal-ext.properties) for the version number. Alternatively, append /c/portal/version to the base URL.Affected if The installed version falls within >= 7.4.3.35 and < 7.4.3.111, or between 2023.Q3.1 and 2023.Q3.6, or between 2023.Q4.0 and 2023.Q4.4, or equals 7.3 or 7.4.
-
Confirm Calendar widget deploymentNavigate to the Control Panel > Apps > Widgets, or inspect the deployed web applications (WAR files) in the application server, and verify whether the Calendar portlet/widget is installed and active.Affected if The Calendar widget is present and enabled in the environment.
-
Identify user profile configurationGo to Control Panel > Users > Users and Organizations, select a user, and examine the profile fields (First Name, Middle Name, Last Name) under the Profile section. These fields store the data displayed in event attendee lists.Affected if User profile fields contain names that could contain unsanitized HTML/JavaScript.
-
Check for event attendee functionalityCreate or view a Calendar event, invite other users as attendees, and then view the event details page where the attendee list is displayed. The vulnerability triggers when viewing this attendee list.Affected if Calendar events with attendees have been created and are viewable by other users.
The environment is affected if the installed LPortal/Liferay version is within the vulnerable ranges AND the Calendar widget with event attendee functionality is in use.
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.1112023.Q3.72023.Q4.5
Update to LPortal 7.4.3.111+, 2023.Q4.5+, or respective patched versions; implement output encoding on user display fields in the Calendar widget.
Lificar Portal 7.4.3.111+; DXP 2023.Q3.7+; DXP 2023.Q4.5+; DXP 7.4 update 93+; DXP 7.3 update 36+
- 1. Identify the exact Lificar Portal or DXP version currently running in your environment
- 2. Based on your current version, determine the appropriate fixed release: For Lificar Portal 7.4.3.x, upgrade to 7.4.3.111 or later; For DXP 2023.Q3.x, upgrade to 2023.Q3.7 or later; For DXP 2023.Q4.x, upgrade to 2023.Q4.5 or later; For DXP 7.3, upgrade to a version after update 35; For DXP 7.4, upgrade to a version after update 92
- 3. Review Lificar's upgrade documentation and release notes for the target version
- 4. Perform a full backup of your database and file system before upgrading
- 5. Test the upgrade in a non-production environment first
- 6. Deploy the upgrade during a scheduled maintenance window
- 7. Verify the Calendar widget functionality after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43820 — 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-43820 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