dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43778

MEDIUM · 6.1 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 2024.q1.21 / 2025.Q1.17 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
A Stored cross-site scripting vulnerability in the Liferay Portal 7.4.0 through 7.4.3.132, and Liferay DXP 2025.Q2.0 through 2025.Q2.11, 2025.Q1.0 through 2025.Q1.16, 2024.Q4.0 through 2024.Q4.7, 2024.Q3.0 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13 and 2024.Q1.1 through 2024.Q1.20 allows an remote authenticated attacker to inject JavaScript through the name of a fieldset in Kaleo Forms Admin. The malicious payload is stored and executed without proper sanitization or escaping.

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 in LQX Portal and DXP allows authenticated attackers to inject malicious JavaScript payloads into the name field of fieldsets within the Kaleo Forms Admin component. The injected payload is stored in the system and executed without proper input sanitization or output escaping when other users access the affected interface.

MitigationUpgrade to a patched version of LQX Portal or DXP that addresses this vulnerability. Until then, restrict access to Kaleo Forms Admin to only trusted administrative users and monitor for suspicious activity.

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:>= 2024.q1.1, < 2024.q1.21>= 2024.q2.0, <= 2024.q2.13>= 2024.Q3.0, <= 2024.Q3.13>= 2024.q4.0, <= 2024.q4.7>= 2025.Q1.0, < 2025.Q1.17>= 2025.Q2.0, < 2025.Q2.12
Liferay PortalApplication
Affected:>= 7.4.0, <= 7.4.3.132

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 the installed Lifer DXP or Portal version
    Access the Lifer Control Panel and navigate to Configuration > Server Information, or check the portal-ext.properties file for the version number
    Affected if The version falls within the affected ranges: 2024.q1.1 to <2024.q1.21, 2024.q2.0 to 2024.q2.13, 2024.Q3.0 to 2024.Q3.13, 2024.q4.0 to 2024.q4.7, 2025.Q1.0 to <2025.Q1.17, 2025.Q2.0 to <2025.Q2.12 for DXP; or 7.4.0 to 7.4.3.132 for Portal
  2. Confirm Kaleo Forms Admin module is deployed
    Navigate to the Lifer Control Panel and check for the Kaleo Forms Admin section under Content > Kaleo Forms Admin, or query the module registry for kaleo-forms-admin
    Affected if The Kaleo Forms Admin component is present and accessible in the installation
  3. Inspect fieldsets in Kaleo Forms Admin for suspicious content
    Navigate to Kaleo Forms Admin in the Control Panel and review all fieldset name entries. Check the database table for Kaleo Forms fieldset definitions if direct database access is available
    Affected if Any fieldset name field contains JavaScript tags, event handlers, or encoded malicious payloads such as <script>, onerror=, onload=, or similar XSS vectors

A user is affected if they run a version within the listed ranges AND have Kaleo Forms Admin enabled with any fieldset entries containing unsanitized script content in the name field.

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 2024.q1.21 / 2025.Q1.17 / 2025.Q2.12 or later
Fixed in 2024.q1.212025.Q1.172025.Q2.12
Interim mitigation

Upgrade to a patched version of LQX Portal or DXP that addresses this vulnerability. Until then, restrict access to Kaleo Forms Admin to only trusted administrative users and monitor for suspicious activity.

Recommended fix High confidence

Lifer DXP 2024.Q1.21+, 2024.Q3.14+, 2024.Q4.8+ or Lifer Portal 7.4.3.133+

  1. 1. Identify the exact Lifeway DXP or Portal version currently running by checking the Control Panel > Configuration > Server Administration > Version
  2. 2. For Digital Experience Platform (DXP) users on 2024.Q1.x line: upgrade to 2024.Q1.21 or later
  3. 3. For DXP users on 2024.Q2.x line: upgrade to 2024.Q3.14 or later (2024.Q2 is end-of-life, jump to Q3)
  4. 4. For DXP users on 2024.Q3.x line: upgrade to 2024.Q3.14 or later
  5. 5. For DXP users on 2024.Q4.x line: upgrade to 2024.Q4.8 or later
  6. 6. For Lifer Portal users on 7.4.x line: upgrade to 7.4.3.133 or later
  7. 7. After upgrade, verify the Kaleo Forms Admin fieldset name functionality works correctly and the XSS vulnerability is remediated
Caveat Review release notes for your specific version jump as minor changes in form behavior may exist; test in non-production first

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

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43778 — 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-43778 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