CVE-2025-43808
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 Commerce component in Liferay Portal 7.3.0 through 7.4.3.112, and Liferay DXP 2023.Q4.0 through 2023.Q4.8, 2023.Q3.1 through 2023.Q3.10, 7.4 GA through update 92, and 7.3 service pack 3 through update 35 saves virtual products uploaded to Documents and Media with guest view permission, which allows remote attackers to access and download virtual products for free via a 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 · high confidenceThe Commerce component in Liferay Portal and DXP improperly saves virtual products uploaded to Documents and Media with guest (unauthenticated) view permissions. This allows remote attackers to directly access and download virtual product files without payment by crafting URLs to the Documents and Media repository.
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>= 2023.Q3.1, <= 2023.Q3.10>= 2023.Q4.0, < 2023.Q4.9= 7.3= 7.4>= 7.4.0, < 7.4.3.113CVSS 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.
-
Check Liferay Portal/DXP versionNavigate to Control Panel > Configuration > Server Administration > Product Information, or check the osgi/state or portal-impl.jar build numberAffected if Version is 7.4.0 through 7.4.3.112, or 2023.Q3.1 through 2023.Q3.10, or 2023.Q4.0 through 2023.Q4.8, or 7.3.x, or 7.4.x (outside 7.4.3.113+)
-
Verify Commerce module is enabledGo to Control Panel > Apps > Apps Manager and check if Commerce is installed and active, or check for Commerce-related OSGi bundlesAffected if Commerce module is installed and active
-
Identify Documents and Media folders with virtual productsNavigate to Content > Documents and Media, locate any virtual product files (typically associated with Commerce products), and note their folder locationsAffected if Virtual product files exist in Documents and Media library
-
Inspect guest/Everyone permissions on Documents and Media foldersFor each folder containing virtual products, go to folder permissions and check if 'Guest' or 'Everyone' role has 'View' or 'View Permissions' access grantedAffected if Guest (unauthenticated) or Everyone role has View permission on folders containing virtual commerce products
-
Test unauthenticated access to virtual product URLsUse an incognito browser window to attempt accessing known virtual product file URLs from Documents and Media (format: /documents/[site-id]/[folder-id]/[file-name])Affected if Files download successfully without authentication or payment
User is affected if running a vulnerable Liferay version with Commerce enabled AND Documents and Media folders containing virtual products have guest/Everyone view permissions configured
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.1132023.Q4.9
Apply the vendor patches (Liferay Portal 7.4.3.113+, DXP 2023.Q4.9+, 2023.Q3.11+, update 93+, or SP3 update 36+) or manually restrict guest/Everyone permissions on Documents and Media folders containing virtual commerce products.
Lificar Portal 7.4.3.113+; DXP 2023.Q4.9+; DXP 2023.Q3.11+ (or subsequent patch); DXP 7.3 update 36+; DXP 7.4 update 93+
- 1. Identify the current Lificar Portal or DXP version by checking the Control Panel > Configuration > Server Administration > Build information
- 2. For Lificar Portal 7.4.x: Upgrade to version 7.4.3.113 or later
- 3. For DXP 2023.Q4.x: Upgrade to version 2023.Q4.9 or later
- 4. For DXP 2023.Q3.x: Upgrade to a version beyond 2023.Q3.10 (contact Lificar for specific patch)
- 5. For DXP 7.3: Apply service pack update 36 or later (contact Lificar for specific patch)
- 6. For DXP 7.4 GA: Apply update 93 or later
- 7. After upgrade, verify that virtual products in Documents and Media no longer have guest view permissions by default
- 8. Test that virtual products require proper authentication and authorization before download
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43808 — 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-43808 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