dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-62275

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-01
Fix available
A fix is available. Upgrade to 7.4.3.112 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Blogs in Liferay Portal 7.4.0 through 7.4.3.111, and older unsupported versions, and Liferay DXP 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.10, 7.4 GA through update 92, and older unsupported versions does not check permission of images in a blog entry, which allows remote attackers to view the images in a blog entry via crafted URL.

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 · moderate confidence

This is an authorization bypass vulnerability where Limerick Portal and DXP fail to perform permission checks when serving images embedded in blog entries. Attackers can access restricted images by directly constructing URLs to blog images without proper authentication or authorization validation.

MitigationApply the vendor-supplied patch or upgrade to a patched version. If immediate patching is not feasible, consider implementing URL access controls or web application firewall rules to restrict direct access to blog image paths while the patch is being deployed.

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:= 7.4= 2023.q3.1= 2023.q3.2= 2023.q3.3= 2023.q3.4= 2023.q3.5= 2023.q3.6= 2023.q3.7= 2023.q3.8= 2023.q3.9= 2023.q3.10= 2023.q4.0
Liferay PortalApplication
Affected:>= 7.4.0, < 7.4.3.112

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Identify Limerick Portal or DXP installed version
    Check the portal's version by reviewing the release.properties file in the Limerick installation directory, or access the Control Panel > Configuration > Server Administration > General to view the portal version.
    Affected if The installed version is 7.4.0 through 7.4.3.111, or matches 7.4, or any 2023.q3.x version through 2023.q3.10, or 2023.q4.0.
  2. Verify blog image serving is enabled
    Confirm that the blog application module is deployed and that image attachments are allowed in blog entries via the Control Panel > Content & Data > Blogs > Configuration.
    Affected if Blog functionality is active and users can add images to blog posts.
  3. Test direct image URL access
    Construct a test URL in the format /blogs/image/<filename> and attempt to access it from an unauthenticated browser session or via curl without providing session credentials.
    Affected if The image loads successfully without requiring authentication or authorization validation.
  4. Inspect access logs for blog image requests
    Review the Limerick access logs (typically in the /logs directory) for requests to /blogs/image/ paths that occur without prior authentication or with invalid session tokens.
    Affected if Log entries show successful GET requests to blog image URLs from unauthenticated sources.

If the portal runs an affected version AND blog images are accessible via direct URL construction without authentication, the environment is vulnerable to CVE-2025-62275.

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.112 or later
Fixed in 7.4.3.112
Interim mitigation

Apply the vendor-supplied patch or upgrade to a patched version. If immediate patching is not feasible, consider implementing URL access controls or web application firewall rules to restrict direct access to blog image paths while the patch is being deployed.

Recommended fix High confidence

Liferay Portal 7.4.3.112 or later; Liferay DXP 2023.Q4.11 / 2023.Q3.11 / 7.4 update 93 or later

  1. 1. Identify the current Liferay Portal or DXP version by checking the liferay-portal.properties or the control panel About section
  2. 2. For Liferay Portal 7.4.x users: Plan upgrade to version 7.4.3.112 or later
  3. 3. For Liferay DXP users: Upgrade to one of the fixed releases - DXP 2023.Q4.11+, DXP 2023.Q3.11+, or DXP 7.4 update 93+
  4. 4. Before upgrading in production, test the upgrade in a staging environment to verify compatibility with custom modules and themes
  5. 5. Back up the database and file system before performing the upgrade
  6. 6. Deploy the new version and verify that blog images now properly enforce permission checks
Caveat Standard upgrade risks apply - test custom plugins/themes for compatibility with the new version before production deployment

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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