dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43761

MEDIUM · 6.1 CVSS v3.1 Published 2025-08-22
Fix available
A fix is available. Upgrade to 7.4.3.132 / 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
A reflected cross-site scripting (XSS) vulnerability in the Liferay Portal 7.4.0 through 7.4.3.131, and Liferay DXP 2024.Q4.0 through 2024.Q4.4, 2024.Q3.1 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.12 and 7.4 GA through update 92 allows an remote non-authenticated attacker to inject JavaScript into the frontend-editor-ckeditor-web/ckeditor/samples/old/ajax.html 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 Limerick Portal and DXP versions 7.4.x through 7.4.3.131 and various 2024 quarterly releases. The vulnerability is located in the CKEditor samples directory at /frontend-editor-ckeditor-web/ckeditor/samples/old/ajax.html, where an unauthenticated remote attacker can inject malicious JavaScript via unsanitized input.

MitigationRemove or restrict access to the CKEditor samples directory (ckeditor/samples/) in production deployments, as these are not intended for production use and represent a known attack surface.

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.1, <= 2024.q3.13>= 2024.Q4.0, < 2024.Q4.5= 7.4
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. Check Liferel Portal/DXP version
    Access the Liferel server administration panel or check the portal-ext.properties file for the version number. The version is typically displayed in the Control Panel > Configuration > Server Administration or can be found in the liferay-*.jar files in the installation directory.
    Affected if The installed version falls within any of these ranges: 7.4.0 to 7.4.3.131 inclusive; 2024.Q1.1 to 2024.Q1.13; 2024.Q2.0 to 2024.Q2.13; 2024.Q3.1 to 2024.Q3.13; 2024.Q4.0 to 2024.Q4.4; or is exactly version 7.4 (without a specific subversion).
  2. Verify CKEditor samples directory exists
    Check if the directory /frontend-editor-ckeditor-web/ckeditor/samples/ exists within the Liferel web application deployment. On typical installations, this would be under the webapps or deploy directory. Specifically verify the presence of ajax.html in the old subdirectory.
    Affected if The directory /frontend-editor-ckeditor-web/ckeditor/samples/old/ajax.html exists on the server file system or is accessible via the web application.
  3. Test accessibility of the vulnerable endpoint
    Attempt to access the URL pattern: https://your-server/frontend-editor-ckeditor-web/ckeditor/samples/old/ajax.html (replace your-server with the actual hostname). Send a request with a test parameter to see if input is reflected unsanitized in the response.
    Affected if The endpoint responds with the ajax.html page and reflects URL parameters in the output without sanitization, indicating the vulnerability is present and exploitable.

A user is affected if the installed Liferel version is within the affected ranges AND the CKEditor samples directory (/frontend-editor-ckeditor-web/ckeditor/samples/old/ajax.html) is present and accessible without authentication.

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.132 / 2024.Q1.13 / 2024.Q4.5 or later
Fixed in 7.4.3.1322024.Q1.132024.Q4.5
Interim mitigation

Remove or restrict access to the CKEditor samples directory (ckeditor/samples/) in production deployments, as these are not intended for production use and represent a known attack surface.

Recommended fix High confidence

Lifer息 Portal 7.4.3.132+ or DXP 2024.Q1.13+/2024.Q2.14+/2024.Q3.14+/2024.Q4.5+ (depending on current version)

  1. 1. Identify the currently installed Limerick Portal or DXP version by checking the Lifer息 Digital Enterprise Platform or Portal administration console
  2. 2. For Lifer息 Portal 7.4.0-7.4.3.131: Upgrade to Lifer息 Portal 7.4.3.132 or later
  3. 3. For DXP 2024.Q1.1-2024.Q1.12: Upgrade to DXP 2024.Q1.13 or later
  4. 4. For DXP 2024.Q2.0-2024.Q2.13: Upgrade to DXP 2024.Q2.14 or later
  5. 5. For DXP 2024.Q3.1-2024.Q3.13: Upgrade to DXP 2024.Q3.14 or later
  6. 6. For DXP 2024.Q4.0-2024.Q4.4: Upgrade to DXP 2024.Q4.5 or later
  7. 7. After upgrade, verify the frontend-editor-ckeditor-web module is updated and the ckeditor/samples/old/ajax.html endpoint no longer reflects unsanitized input
  8. 8. Test that legitimate CKEditor functionality still works as expected after the upgrade
Caveat Standard upgrade risks apply - review Lifer息's upgrade documentation for your specific version path, especially for major version jumps

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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