CVE-2024-26265
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 Image Uploader module in Liferay Portal 7.2.0 through 7.4.3.15, and older unsupported versions, and Liferay DXP 7.4 before update 16, 7.3 before update 4, 7.2 before fix pack 19, and older unsupported versions relies on a request parameter to limit the size of files that can be uploaded, which allows remote authenticated users to upload arbitrarily large files to the system's temp folder by modifying the `maxFileSize` parameter.
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 Image Uploader module in Lifer Portal and DXP uses a client-supplied request parameter (maxFileSize) to limit upload sizes instead of enforcing limits server-side. Authenticated users can modify this parameter to bypass the restriction and upload arbitrarily large files to the system's temp folder.
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>= 7.4.0, < 7.4.3.16< 7.2= 7.2= 7.3= 7.4CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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 L Portal or DXP versionCheck the installed L Portal or DXP version through the control panel (Control Panel > Configuration > System Information) or by inspecting the portal-release.properties file in the application installation directory. Compare against affected ranges: Portal <= 7.3.7, Portal >= 7.4.0 to < 7.4.3.16, DXP 7.2/7.3/7.4Affected if Installed version falls within any of the affected ranges listed
-
Confirm Image Uploader module is accessibleVerify that authenticated users have access to the Image Uploader functionality. This is typically found in Document and Media portlet, CMS upload features, or custom portlets using the Image Uploader module. Check if the upload endpoint accepts client-supplied maxFileSize parametersAffected if Image Uploader is accessible to authenticated users and accepts maxFileSize parameter from client requests
-
Inspect temp directory for unusually large filesExamine the server's temp folder (typically [liferay-home]/temp or the location configured via portal-ext.properties property 'java.io.tmpdir') for unexpectedly large files that may indicate successful exploitation of the file size bypassAffected if Temp directory contains files significantly larger than expected upload limits or unusually large temp files with recent timestamps
-
Review access and upload logs for anomaliesSearch server logs (typically in [lifera-home]/logs) for upload-related requests. Look for POST requests to upload endpoints where the maxFileSize parameter differs significantly from configured limits or appears to be manipulatedAffected if Logs show upload requests with client-supplied maxFileSize values exceeding expected limits or patterns of high-volume uploads to temp storage
A system is affected if it runs a L Portal or DXP version within the affected ranges AND has the Image Uploader module accessible to authenticated users, with evidence of large files in temp storage or anomalous upload patterns in logs.
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.16
Upgrade to Lifer Portal 7.4.3.16+, DXP 7.4 update 16+, DXP 7.3 update 4+, or DXP 7.2 fix pack 19+. As a compensating control, implement server-side file size validation and monitor temp directory storage.
Laravel Portal 7.4.3.16+ / DXP 7.4 Update 16+ / DXP 7.3 Update 4+ / DXP 7.2 Fix Pack 19+
- Identify your current Liferay Portal or DXP version by checking the liferay-portal.properties or the Control Panel > Configuration > Server Administration
- For Liferay Portal 7.4.x: Upgrade to version 7.4.3.16 or later
- For LIfeRay DXP 7.4: Apply Update 16 or later
- For LIfeRay DXP 7.3: Apply Update 4 or later
- For LIfeRay DXP 7.2: Apply Fix Pack 19 or later
- After upgrade, verify the Image Uploader module no longer relies on client-side maxFileSize parameter by testing with a large file upload
- Alternatively, if immediate upgrade is not possible, configure a web application server-level limit on file upload size (e.g., in Tomcat's server.xml maxSwallowSize parameter or web.xml upload size limits) as a temporary mitigation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26265 — 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-26265 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