CVE-2025-43764
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 · uneditedSelf-ReDoS (Regular expression Denial of Service) exists with Role Name search field of Kaleo Designer portlet JavaScript in Liferay Portal 7.4.0 through 7.4.3.131, and Liferay DXP 2024.Q4.0 through 2024.Q4.1, 2024.Q3.0 through 2024.Q3.13, 2024.Q2.1 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.20 and 7.4 GA through update 92, which allows authenticated users with permissions to update Kaleo Workflows to enter a malicious Regex pattern causing their browser to hang for a very long time.
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 confidenceSelf-ReDoS vulnerability in Liferay's Kaleo Designer portlet JavaScript where the Role Name search field accepts malicious Regex patterns. Authenticated users with Kaleo Workflow permissions can input crafted regex causing catastrophic backtracking in the browser's regex engine, leading to extended browser hang.
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>= 2024.Q1.1, <= 2024.Q1.20>= 2024.q2.0, <= 2024.q2.13>= 2024.q3.1, <= 2024.q3.13>= 2024.Q4.0, < 2024.Q4.2= 7.4>= 7.4.0, < 7.4.3.132CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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.
-
Identify Liferays versionCheck the Liferays portal or DXP version in the Control Panel under Configuration > Server Information, or inspect the liferay-oscæ-tomcat bundle version propertiesAffected if The installed version falls within the affected ranges: DXP 2024.Q1.1 to 2024.Q1.20, 2024.q2.0 to 2024.q2.13, 2024.q3.1 to 2024.q3.13, 2024.Q4.0 to 2024.Q4.1, or version 7.4; Portal 7.4.0 to 7.4.3.131
-
Confirm Kaleo Workflow is enabledNavigate to Control Panel > Workflow > Process Builder or inspect the Kaleo workflow engine configuration in the OSGi consoleAffected if Kaleo workflow engine is active and the workflow definition framework is loaded
-
Verify Kaleo Designer portlet is deployedCheck for the Kaleo Designer portlet in the Liferays UI under Control Panel > Workflow > Kaleo Designer, or query the OSGi bundle list for com_liferays_kaleo_designerAffected if The Kaleo Designer portlet is present in the running instance
-
Check for Kaleo Workflow admin permissionsReview user roles in Control Panel > Users and Permissions > Role Definitions, looking for roles with Kaleo Workflow permissions such as Kaleo Administrator or Workflow ViewerAffected if Any authenticated users possess Kaleo Workflow permissions enabling access to the Role Name search field in Kaleo Designer
-
Locate the vulnerable Role Name search componentAccess the Kaleo Designer interface and identify the Role Name search field used for filtering workflow roles, typically found in the role assignment or task assignment sectionsAffected if The Role Name search field is accessible and accepts user input for filtering roles
You are affected if your Liferays version matches the affected ranges AND Kaleo Workflow is enabled with the Kaleo Designer portlet accessible to authenticated users with workflow permissions.
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.1322024.Q4.2
Apply vendor patch when available. As interim measure, restrict Kaleo Workflow administration permissions to minimal required users, or consider temporarily disabling the Role Name search functionality until patched.
2024.Q4.2 (DXP) or 7.4.3.132 (Portal)
- Identify the exact Liferay product and version currently installed (Portal or DXP with specific quarterly version)
- For Lifter DXP: Upgrade to version 2024.Q4.2 or later
- For Liferay Portal: Upgrade to version 7.4.3.132 or later
- After upgrade, verify the Kaleo Designer portlet functionality remains intact
- Confirm the Role Name search field no longer causes browser hang with complex regex patterns
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43764 — 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-43764 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