dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43829

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-08
Fix available
A fix is available. Upgrade to 7.4.3.112 / 2023.q3.9 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Stored cross-site scripting (XSS) vulnerability in diagram type products in Commerce in Liferay Portal 7.4.3.18 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.8, and 7.4 update 18 through update 92 allows remote attackers to inject arbitrary web script or HTML via a crafted payload injected into a SVG file.

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

Stored cross-site scripting (XSS) vulnerability in LXR Portal and DXP Commerce module allows remote attackers to inject malicious JavaScript or HTML through SVG file uploads in diagram type products. The payload is stored and executes when other users view the affected diagrams.

MitigationUpgrade LXR Portal to 7.4.3.112 or later, and DXP to patched versions beyond 2023.Q4.5/2023.Q3.8/7.4 update 92; alternatively, implement SVG sanitization on file uploads in the Commerce diagram feature.

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:>= 2023.q3.1, < 2023.q3.9>= 2023.q4.0, < 2023.q4.6= 7.3= 7.4
Liferay PortalApplication
Affected:>= 7.4.3.18, < 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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify LXR Portal or DXP version
    Check the product version through the Liferay Administration console (Control Panel > Configuration > System Information) or look for version files in the Liferay installation directory. For LXR Portal, check the osgi/state or portal-release.properties file. For DXP, check the dxp-version.properties or liferay-home/WEB-INF/classes/portal-ext.properties.
    Affected if The installed version falls within any of these ranges: LXR Portal >= 7.4.3.18 and < 7.4.3.112; DXP 2023.q3.1 through < 2023.q3.9; DXP 2023.q4.0 through < 2023.q4.6; DXP 7.3.x or 7.4.x.
  2. Verify Commerce module is enabled
    Navigate to Control Panel > Apps > App Manager in the Liferay admin console. Search for 'Commerce' or 'LXR' module. Alternatively, check the osgi/modules directory for commerce-related bundles (.jar files) that contain 'commerce' in the filename.
    Affected if The Commerce module is installed and enabled, which provides the diagram feature where SVG uploads can be performed.
  3. Check if diagram product type is accessible
    In the L Commerce admin panel, navigate to Catalog > Products > Add Product. Observe whether 'Diagram' is available as a product type option. Diagrams in LXR/DXP Commerce allow visual product configuration with image/file uploads.
    Affected if The Diagram product type is available and users have permission to create diagram-type products.
  4. Confirm SVG upload capability in diagram feature
    Create or edit a diagram product. Look for options to upload files (typically in the diagram builder or image upload sections). Attempt to upload a test SVG file or inspect the file type restrictions in the Commerce configuration under Settings > Catalogs > File Upload restrictions.
    Affected if SVG file uploads are permitted in the diagram feature without server-side sanitization.

You are affected if your LXR Portal version is between 7.4.3.18 and 7.4.3.111, or your DXP version matches 2023.Q3.1-2023.Q3.8, 2023.Q4.0-2023.Q4.5, 7.3.x, or 7.4.x, AND the Commerce module with diagram functionality is enabled and allows SVG uploads.

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 / 2023.q3.9 / 2023.q4.6 or later
Fixed in 7.4.3.1122023.q3.92023.q4.6
Interim mitigation

Upgrade LXR Portal to 7.4.3.112 or later, and DXP to patched versions beyond 2023.Q4.5/2023.Q3.8/7.4 update 92; alternatively, implement SVG sanitization on file uploads in the Commerce diagram feature.

Recommended fix High confidence

Liferay DXP 2023.Q3.9, DXP 2023.Q4.6, or Liferay Portal 7.4.3.112 (depending on product line)

  1. 1. Identify the currently installed Lifford DXP or Portal version by checking the Liferay Portal administration console or bundle information.
  2. 2. For DXP 2023.Q3.x deployments: Upgrade to version 2023.Q3.9 or later to resolve the SVG injection vulnerability.
  3. 3. For DXP 2023.Q4.x deployments: Upgrade to version 2023.Q4.6 or later to resolve the SVG injection vulnerability.
  4. 4. For Liferay Portal 7.4.3.x deployments: Upgrade to version 7.4.3.112 or later to resolve the SVG injection vulnerability.
  5. 5. After upgrading, verify that the Commerce diagram product functionality works correctly with SVG files.
  6. 6. Test that the XSS fix properly sanitizes SVG file uploads in the Commerce diagram type products.
Caveat Review Liferay upgrade documentation for any configuration or compatibility changes between versions; minor version upgrades typically have minimal breaking changes

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

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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