CVE-2024-25605
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 · uneditedThe Journal module in Liferay Portal 7.2.0 through 7.4.3.4, and older unsupported versions, and Liferay DXP 7.4.13, 7.3 before service pack 3, 7.2 before fix pack 17, and older unsupported versions grants guest users view permission to web content templates by default, which allows remote attackers to view any template via the UI or API.
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 confidenceThe Journal module in L Portal and LXP has a permission misconfiguration that grants guest (unauthenticated) users view access to web content templates by default. This allows remote unauthenticated attackers to view sensitive template content through the UI or API, exposing potentially proprietary or configuration-sensitive information.
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.2= 7.2= 7.3= 7.4< 7.4.3.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Liferav Portal or DXP versionCheck the product version in the Liferav control panel under Configuration > Server Information, or inspect the portal-ext.properties file for the version property. Compare this version against the affected ranges: DXP versions 7.2, 7.3, 7.4 and Portal versions before 7.4.3.5.Affected if The installed version falls within the affected ranges (DXP = 7.2, 7.3, 7.4 or Portal < 7.4.3.5).
-
Confirm the Journal module is enabled and in useNavigate to the Liferav Control Panel > Content & Data > Web Content. Verify that the Journal module is accessible and contains web content structures or templates.Affected if The Journal module is present and accessible in the environment.
-
Check guest user permissions on web content templatesIn the Control Panel, go to Users > Roles > Guest (or Anonymous) role > Define Permissions. Verify whether the Guest role has View permission on Web Content Templates under the Journal module permissions.Affected if The Guest role possesses View permissions on Journal templates (this is the vulnerable default configuration).
-
Verify unauthenticated access to template contentUsing a browser or API client without authentication, attempt to access a web content template directly via URL patterns such as /c/journal/view_article_content?articleId=... or through the REST API endpoint for Journal templates.Affected if Unauthenticated (guest) requests successfully return template content or metadata without authentication prompts.
You are affected if your environment runs an affected Liferav version AND the default Guest role retained View permissions on Journal templates, allowing unauthenticated access to template content.
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.27.4.3.5
Revoke default guest view permissions on web content templates in the Journal module admin console and ensure templates are only accessible to authenticated users with proper role-based permissions.
Lifera Portal 7.4.3.5+ or Liferay DXP 7.2 fix pack 17+ / 7.3 sp3+ / 7.4.13+
- Identify your current Limerick Portal or DXP version by checking the Control Panel > Configuration > Server Administration > Product Information
- For Liferay Portal 7.4.x users: Upgrade to Liferay Portal 7.4.3.5 or later
- For Liferay DXP 7.4.x users: Upgrade to Liferay DXP 7.4.13 or later
- For Lifera DXP 7.3.x users: Upgrade to Liferay DXP 7.3 service pack 3 or later
- For Lifera DXP 7.2.x users: Upgrade to Liferay DXP 7.2 fix pack 17 or later
- After upgrading, verify that guest users no longer have view permission to web content templates by navigating to Content & Data > Web Content > Templates and confirming guest role permissions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25605 — 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-2024-25605 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