Digital Experience PlatformApplication · Liferay

CVE-2025-4604

MEDIUM · 6.1 CVSS v3.1 Published 2025-08-04
Fix available
A fix is available. Upgrade to after 2025.q1.15 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
The vulnerable code can bypass the Captcha check in Liferay Portal 7.4.3.80 through 7.4.3.132, and Liferay DXP 2024.Q1.1 through 2024.Q1.19, 2024.Q2.0 through 2024.Q2.13, 2024.Q3.0 through 2024.Q3.13, 2024.Q4.0 through 2024.Q4.7, 2025.Q1.0 through 2025.Q1.15 and 7.4 update 80 through update 92 and then attackers can run scripts in the Gogo shell

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

Lifray Portal and DXP contain a Captcha validation bypass vulnerability in versions 7.4.3.80 through 7.4.3.132 and multiple quarterly updates. The flawed Captcha check can be circumvented, allowing unauthenticated attackers to execute arbitrary scripts through the Gogo shell interface.

MitigationApply available vendor patches or upgrade to fixed versions beyond 7.4.3.132, 7.4 update 92, and 2025.Q1.15 respectively. Restrict network access to the Gogo shell endpoint as an additional hardening measure.

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.19>= 2024.q2.0, <= 2024.q2.13>= 2024.Q3.0, <= 2024.Q3.13>= 2024.q4.0, <= 2024.q4.7>= 2025.q1.0, <= 2025.q1.15= 7.4
Liferay PortalApplication
Affected:>= 7.4.3.80, <= 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. Determine Liferay Portal version
    Locate the version file or check the control panel: look for portal-impl.jar in the LIFERAY_HOME/tomcat/webapps/ROOT/WEB-INF/lib directory, or navigate to Control Panel > Configuration > Server Administration > Server > Liferay Portal version
    Affected if The installed version falls within 7.4.3.80 through 7.4.3.132, or within the quarterly update ranges (2024.q1.1-2024.q1.19, 2024.q2.0-2024.q2.13, 2024.q3.0-2024.q3.13, 2024.q4.0-2024.q4.7, or 2025.q1.0-2025.q1.15)
  2. Verify if Gogo shell endpoint is network accessible
    Check network exposure of port 11311 (default Gogo shell port) by reviewing firewall rules, reverse proxy configuration, and server access controls. Attempt a local test: telnet localhost 11311 or curl http://localhost:11311 if remote access is unrestricted
    Affected if The Gogo shell port 11311 is reachable from untrusted networks or the endpoint is exposed via web without proper access restrictions
  3. Confirm guest/virtual user registration is enabled
    Navigate to Control Panel > Users > Users and Permissions > Guest role, or check portal-ext.properties for the key 'company.security.strangers.verify' or 'users.screen.name.allow.numeric'. Alternatively, inspect the JSON response when accessing the Captcha endpoint directly
    Affected if Guest users can register or virtual hosts are enabled, allowing unauthenticated attackers to reach the Captcha-protected form that can be bypassed

Your environment is affected if the Liferay version matches the affected ranges AND the Gogo shell interface is network-accessible to untrusted users, enabling unauthenticated script execution via the Captcha bypass.

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 a release after 2025.q1.15
Interim mitigation

Apply available vendor patches or upgrade to fixed versions beyond 7.4.3.132, 7.4 update 92, and 2025.Q1.15 respectively. Restrict network access to the Gogo shell endpoint as an additional hardening measure.

Recommended fix Moderate confidence

Lifer DXP 2024.Q1.20+, 2024.Q2.14+, 2024.Q3.14+, 2024.Q4.8+, 2025.Q1.16+ or Lifer Portal 7.4.3.133+ / 7.4.3.u95+

  1. 1. Identify the currently installed Liferay DXP or Portal version using the admin console or bundle information.
  2. 2. For Lifter DXP 2024.Q1.x: upgrade to 2024.Q1.20 or later.
  3. 3. For Lifer DXP 2024.Q2.x: upgrade to 2024.Q2.14 or later.
  4. 4. For Lifer DXP 2024.Q3.x: upgrade to 2024.Q3.14 or later.
  5. 5. For Lifer DXP 2024.Q4.x: upgrade to 2024.Q4.8 or later.
  6. 6. For Lifer Portal 7.4.3.80-7.4.3.132: upgrade to 7.4.3.133 or later (or consider moving to a newer update train such as 7.4.3.u95+).
  7. 7. After upgrade, verify the Captcha protection is functioning correctly in the Gogo shell access areas.
  8. 8. Review user permissions to ensure only authorized users can access the Gogo shell.
Caveat Review release notes for breaking changes between version ranges; major version upgrades may require compatibility testing

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

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing5.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,430
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-4604 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