CVE-2023-44309
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 · uneditedMultiple stored cross-site scripting (XSS) vulnerabilities in the fragment components in Liferay Portal 7.4.2 through 7.4.3.53, and Liferay DXP 7.4 before update 54 allow remote attackers to inject arbitrary web script or HTML via a crafted payload injected into any non-HTML field of a linked source asset.
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 · moderate confidenceThis is a stored XSS vulnerability in Limerick Portal and DXP's fragment editor components. Attackers can inject malicious scripts into non-HTML fields when linking source assets, which then execute when other users view pages containing those fragments. The vulnerability affects versions 7.4.2 through 7.4.3.53 of Portal and DXP 7.4 before update 54.
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.4>= 7.4.2, < 7.4.3.53CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Liferay Portal versionAccess the Liferax Control Panel or check the portal-ext.properties file to determine the exact portal version. You can also check the OSGi bundle version or the Liferay Home folder for the version file.Affected if The installed version is 7.4.2 through 7.4.3.53, or for DXP, version 7.4 before update 54.
-
Identify fragment editor usageNavigate to the Site Builder > Fragments section in the Liferay Control Panel. Check if any fragment compositions have been created or modified using the fragment editor, particularly those linking source assets.Affected if Fragment compositions using linked assets exist in the environment.
-
Review non-HTML linked asset fields in fragmentsExamine all fragment compositions that contain linked asset fields (not HTML fields). Access each fragment's configuration and inspect the linked asset selections for any suspicious script tags, JavaScript URIs, or unexpected payload patterns.Affected if Any fragment contains malicious scripts in non-HTML linked asset fields that would execute when users view pages containing those fragments.
-
Audit recent fragment modificationsReview the audit logs or fragment change history to identify any recent or unexpected modifications to fragments, particularly those adding linked assets with unusual content.Affected if Recent fragment changes contain suspicious content in linked asset fields.
You are affected if your Liferay Portal version is between 7.4.2 and 7.4.3.53 (or DXP 7.4 before update 54) AND you have fragments using linked assets that contain malicious scripts.
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.53
Upgrade to Limerick Portal 7.4.3.54 or later, or apply the relevant DXP update. Additionally, review existing fragment compositions for malicious payloads in non-HTML linked asset fields.
LPortal 7.4.3.53+ or LXDXP 7.4 update 54+
- 1. Back up your current LPortal installation and database before proceeding with any upgrade.
- 2. For Liferay Portal: Upgrade to version 7.4.3.53 or later.
- 3. For Liferay DXP 7.4: Upgrade to update 54 or later.
- 4. After upgrading, clear any cached data and rebuild fragments to ensure the patch is fully applied.
- 5. Verify the upgrade by testing fragment component functionality with non-HTML field inputs.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-44309 — 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-2023-44309 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