CVE-2025-43767
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 · uneditedOpen Redirect vulnerability in /c/portal/edit_info_item parameter redirect in Liferay Portal 7.4.3.86 through 7.4.3.131, and Liferay DXP 2024.Q3.1 through 2024.Q3.9, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.12 and 7.4 update 86 through update 92 allows an attacker to exploit this security vulnerability to redirect users to a malicious site.
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 confidenceOpen redirect vulnerability in Liferays /c/portal/edit_info_item endpoint allows manipulation of the 'redirect' parameter to redirect users to attacker-controlled external sites. Insufficient validation of the redirect URL destination permits relative or absolute URLs to pass through unchecked.
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.13>= 2024.q2.0, <= 2024.q2.13>= 2024.Q3.1, < 2024.Q3.10= 7.4>= 7.4.3.86, < 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Liferay Portal versionAccess the Liferay control panel or check the portal-ext.properties file for the version property. Alternatively, access the /c/portal/layout page or check the WAR file manifest for version information.Affected if The version is >= 7.4.3.86 and < 7.4.3.132
-
Identify the installed Liferay DXP version and update levelAccess the Liferay DXP control panel or check the Liferay home directory for version metadata. Liferay DXP typically displays the version in the product information section of the control panel.Affected if The version is 7.4, or falls within >= 2024.Q1.1 and < 2024.Q1.13, >= 2024.Q2.0 and <= 2024.Q2.13, or >= 2024.Q3.1 and < 2024.Q3.10
-
Confirm the /c/portal/edit_info_item endpoint is accessibleAttempt to access the /c/portal/edit_info_item endpoint via a web browser or curl request. This endpoint is typically available to authenticated users with profile editing permissions.Affected if The endpoint responds and accepts requests, indicating it is publicly or internally accessible
-
Test the redirect parameter for unvalidated redirectionSend a request to /c/portal/edit_info_item with a redirect parameter set to an external domain (for example: ?redirect=https://example.com). Observe whether the application allows the external URL without validation or blocking.Affected if The redirect parameter accepts and reflects external URLs without validation, allowing redirection to arbitrary domains
The environment is affected if the installed Liferay Portal or DXP version falls within any of the affected version ranges AND the /c/portal/edit_info_item endpoint accepts unvalidated external URLs in the redirect parameter.
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.Q1.132024.Q3.10
Upgrade to Liferays patched versions (Portal 7.4.3.132+, DXP 2024.Q3.10+, 2024.Q2.14+, 2024.Q1.13+, or 7.4 update 93+). As a compensating control, implement URL validation or WAF rules to restrict the redirect parameter to trusted domains.
Lifter Portal: 7.4.3.132; DXP 2024.Q1.13; DXP 2024.Q2.14; DXP 2024.Q3.10; DXP 7.4 update 93
- 1. Identify the currently installed Liferay Portal or DXP version using the Control Panel or server logs
- 2. For Liferay Portal 7.4.3.86 through 7.4.3.131: upgrade to version 7.4.3.132 or later
- 3. For Liferay DXP 2024.Q1.x (2024.Q1.1 through 2024.Q1.12): upgrade to 2024.Q1.13 or later
- 4. For Liferay DXP 2024.Q2.x (2024.Q2.0 through 2024.Q2.13): upgrade to 2024.Q2.14 or later
- 5. For Lirector DXP 2024.Q3.x (2024.Q3.1 through 2024.Q3.9): upgrade to 2024.Q3.10 or later
- 6. For Lirector DXP 7.4 (updates 86-92): upgrade to update 93 (7.4.3.132) or later
- 7. After upgrade, verify the /c/portal/edit_info_item redirect parameter properly rejects external URLs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43767 — 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-43767 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