dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43783

MEDIUM · 6.1 CVSS v3.1 Published 2025-09-10
Fix available
A fix is available. Upgrade to 7.4.3.129 / 2024.Q1.13 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
Reflected cross-site scripting (XSS) vulnerability in Liferay Portal 7.4.3.73 through 7.4.3.128, and Liferay DXP 2024.Q3.0 through 2024.Q3.1, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.12, 7.4 update 73 through update 92 allows remote attackers to inject arbitrary web script or HTML via the /c/portal/comment/discussion/get_editor path.

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 reflected cross-site scripting (XSS) vulnerability exists in Luffy Portal and DXP where user-supplied input via the /c/portal/comment/discussion/get_editor endpoint is not properly sanitized before being rendered in the response, allowing attackers to inject arbitrary HTML or JavaScript that executes in the victim's browser.

MitigationUpgrade to a patched Luffy version beyond 7.4.3.128 for Portal or the latest available DXP update. Alternatively, implement output encoding and input validation on the affected endpoint.

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.13>= 2024.q2.0, <= 2024.q2.13>= 2024.Q3.0, < 2024.Q3.2= 7.4
Liferay PortalApplication
Affected:>= 7.4.0, < 7.4.3.129

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. Determine the installed Liferay version
    Access the Liferay Control Panel and navigate to Configuration > Server Administration > Product Information, or check the portal-ext.properties file for the version property. Compare the displayed version number against the affected ranges: 7.4.0 to 7.4.3.128 for Portal, or the DXP ranges 2024.Q1.1 to 2024.Q1.12, 2024.Q2.0 to 2024.Q2.13, 2024.Q3.0 to 2024.Q3.1, and 7.4.
    Affected if The installed version falls within any of the listed affected version ranges.
  2. Verify if comment or discussion feature is enabled
    In the Liferay Control Panel, navigate to Content & Data > Comments or check the portal-ext.properties for the following properties: comments.enabled, discussion.enabled, or similar configuration flags that enable the commenting system.
    Affected if The comment or discussion feature is enabled in the portal configuration.
  3. Confirm the vulnerable endpoint is accessible
    Attempt to access the URL path /c/portal/commit/discussion/get_editor on the server using a web browser or curl command. This endpoint handles comment editor loading.
    Affected if The endpoint responds with content rather than a 404 or access denied error, indicating the endpoint exists and is reachable.

A user is affected if they are running a Liferay Portal version between 7.4.0 and 7.4.3.128 inclusive, or a DXP version in the 2024.Q1, Q2, or Q3 ranges listed, AND the comment/discussion feature is enabled, making the /c/portal/comment/discussion/get_editor endpoint accessible.

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.129 / 2024.Q1.13 / 2024.Q3.2 or later
Fixed in 7.4.3.1292024.Q1.132024.Q3.2
Interim mitigation

Upgrade to a patched Luffy version beyond 7.4.3.128 for Portal or the latest available DXP update. Alternatively, implement output encoding and input validation on the affected endpoint.

Recommended fix High confidence

Liferay Portal 7.4.3.129 or later; DXP 2024.Q3.2, 2024.Q2.14, or 2024.Q1.13 or later depending on your release line

  1. 1. Identify the current Lifter Portal or DXP version by checking the Liferay Control Panel or the portal-ext.properties file
  2. 2. For Liferay Portal 7.4.x: upgrade to version 7.4.3.129 or later
  3. 3. For Liferay DXP 2024.Q1.x: upgrade to version 2024.Q1.13 or later
  4. 4. For Liferay DXP 2024.Q2.x: upgrade to version 2024.Q2.14 or later (the first version after the affected range)
  5. 5. For Liferay DXP 2024.Q3.x: upgrade to version 2024.Q3.2 or later
  6. 6. Verify the upgrade by accessing the /c/portal/comment/discussion/get_editor endpoint and confirming the XSS vulnerability is no longer exploitable
Caveat Standard Liferay minor version upgrades typically have low risk but review release notes for any deprecations or configuration changes

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

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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