dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43812

MEDIUM · 5.4 CVSS v3.1 Published 2025-09-29
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
Cross-site scripting (XSS) vulnerability in web content template in Liferay Portal 7.4.3.4 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.4, 2023.Q3.1 through 2023.Q3.8, and 7.4 GA through update 92 allows remote authenticated users to inject arbitrary web script or HTML via a crafted payload injected into a web content structure's Name text field

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

A stored cross-site scripting (XSS) vulnerability in Limerick Portal and DXP allows authenticated users to inject arbitrary JavaScript or HTML into the Name text field of web content structures. This malicious payload is stored and executes in the browsers of other users who view the affected content.

MitigationApply the vendor-supplied patches or upgrade to a Limerick version beyond 7.4.3.111 (Portal) or beyond the specified DXP update levels to remediate this vulnerability.

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.5= 7.4
Liferay PortalApplication
Affected:>= 7.4.3.4, < 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 your Lifer Portal or DXP version
    Log into the Control Panel and navigate to Configuration > Server Administration > Index, or check the portal-ext.properties file for the version property, or query the OSGi console with 'lb | grep liferay.portal'. Compare the version number to the affected ranges: Portal 7.4.3.4 through 7.4.3.111, or DXP 2023.q3.1 through 2023.q3.8, DXP 2023.Q4.0 through 2023.Q4.4, or DXP 7.4.
    Affected if The installed version falls within any of the listed vulnerable version ranges
  2. Confirm Web Content Structures are accessible
    In the Control Panel, navigate to Content & Data > Web Content > Structures. Verify that the Structures section is present and accessible to authenticated users with content creation permissions.
    Affected if Web Content Structures feature is enabled and users have permission to create or edit structures
  3. Inspect existing web content structures for malicious Name field payloads
    In the Structures section, review each structure's Name field. Look for unexpected characters such as <script>, javascript:, onerror=, or other HTML/JavaScript syntax that may indicate injected XSS payloads.
    Affected if Any web content structure contains suspicious JavaScript or HTML tags in its Name field
  4. Check recent structure modifications
    Review the structure audit log or recent activity for any unexpected changes to structure names, particularly those containing encoded or unusual characters.
    Affected if Recent structure name changes contain XSS payload patterns

You are affected if your Lifer Portal version is 7.4.3.4-7.4.3.111 or your DXP version matches the 2023.q3.1-2023.q3.8, 2023.Q4.0-2023.Q4.4, or 7.4 ranges, and any web content structure Name field contains stored malicious scripts.

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.5 or later
Fixed in 7.4.3.1122023.q3.92023.Q4.5
Interim mitigation

Apply the vendor-supplied patches or upgrade to a Limerick version beyond 7.4.3.111 (Portal) or beyond the specified DXP update levels to remediate this vulnerability.

Recommended fix High confidence

Lifer DXP: 2023.Q3.9, 2023.Q4.5, or 7.4 update 93+; Lifer Portal: 7.4.3.112+

  1. Identify the currently installed Lifer DXP or Portal version and product line (DXP vs Portal)
  2. For Lifer DXP 2023.Q3.x: Upgrade to version 2023.Q3.9 or later
  3. For Lifer DXP 2023.Q4.x: Upgrade to version 2023.Q4.5 or later
  4. For Lifer DXP 7.4: Upgrade to update 93 or later (the fix addresses update 92 and earlier)
  5. For Lifer Portal 7.4.3.x: Upgrade to version 7.4.3.112 or later
  6. After upgrade, verify the web content structure name field properly sanitizes input

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
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
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,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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