CVE-2025-62266
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 · uneditedBy default, Liferay Portal 7.4.0 through 7.4.3.119, and older unsupported versions, and Liferay DXP 2024.Q1.1 through 2024.Q1.5, 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.10, 7.4 GA through update 92, and older unsupported versions is vulnerable to DNS rebinding attacks, which allows remote attackers to redirect users to arbitrary external URLs. This vulnerability can be mitigated by changing the redirect URL security from IP to domain.
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 confidenceLiferay Portal and DXP are vulnerable to DNS rebinding attacks that allow remote attackers to redirect users to arbitrary external URLs. The vulnerability exists because the redirect URL security defaults to IP-based validation, which can be bypassed through DNS rebinding techniques where an attacker controls DNS responses to map a domain to different IP addresses over time.
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= 7.3= 7.4= 2023.q3.1= 2023.q3.2= 2023.q3.3= 2023.q3.4= 2023.q3.5= 2023.q3.6= 2023.q3.7= 2023.q4.0= 2023.q4.1= 2023.q4.2>= 7.4.0, < 7.4.3.110CVSS 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 Limerick product and versionLocate the Limerick installation and check the version. In the Limerick Control Panel, go to Configuration > Server Administration > Product Information, or check the version file in the Limerick home directory.Affected if The version is Limerick DXP 7.3, 7.4, or any 2023.q3.x through 2023.q4.x release, OR Limerick Portal version 7.4.0 through 7.4.3.109.
-
Locate redirect URL security configurationAccess the Limerick Control Panel and navigate to Configuration > System Settings > Security > Security Navigation. Alternatively, check the portal-ext.properties or portal-setup-wizard.properties file in the Limerick home directory for the property that controls redirect URL validation.Affected if The configuration uses IP-based validation for redirect URLs, which is the default setting.
-
Verify redirect URL security modeIn System Settings, check the 'Redirect URL Security' configuration. Look for a setting that specifies whether validation is based on IP addresses or domains. In properties files, search for a property related to redirect URL validation mode.Affected if The validation mode is set to allow redirects based on IP address matching rather than domain matching.
-
Confirm external redirect capability is enabledCheck if the system allows redirects to external URLs. In System Settings, verify the 'Redirect URL Security' entries include allowed host patterns or the IP-based validation is actively being used for redirect handling.Affected if External redirects are processed through the IP-based validation mechanism, making them vulnerable to DNS rebinding attacks.
You are affected if your Limerick version falls within the listed ranges AND the redirect URL security is configured to use IP-based validation (the default) rather than domain-based validation.
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.110
Change the redirect URL security setting from IP-based validation to domain-based validation in the Liferay configuration. This configuration change prevents attackers from bypassing redirect validation through DNS rebinding.
Liferay Portal 7.4.3.110+ or Liferay DXP 2024.Q1.6+/2023.Q4.11+/2023.Q3.11+/7.4 update 93+
- 1. Identify the exact Lifter Portal or DXP version currently deployed using the Server Administration panel or the osgi/state endpoint
- 2. For Liferay Portal 7.4.x users: Upgrade to Liferay Portal 7.4.3.110 or later to resolve the open redirect vulnerability
- 3. For Liferay DXP users: Upgrade to a version beyond the affected ranges - DXP 2024.Q1.6+, 2023.Q4.11+, or 2023.Q3.11+ (or the equivalent update beyond update 92 for DXP 7.4 GA)
- 4. After upgrade, verify the redirect URL security setting by navigating to Control Panel > System Settings > Security > Security Pages and verifying the redirect URL configuration
- 5. Test that legitimate redirects still function correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62266 — 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-62266 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