CVE-2023-47795
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 · uneditedStored cross-site scripting (XSS) vulnerability in the Document and Media widget in Liferay Portal 7.4.3.18 through 7.4.3.101, and Liferay DXP 2023.Q3 before patch 6, and 7.4 update 18 through 92 allows remote authenticated users to inject arbitrary web script or HTML via a crafted payload injected into a document's “Title” 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 confidenceStored XSS vulnerability in Lifer Portal/DXP's Document and Media widget allows authenticated users to inject malicious scripts into a document's Title field. The payload persists and executes when other users view the document, enabling session hijacking or phishing attacks.
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.3.18, < 7.4.3.102= 7.4= 2023.q3.0= 2023.q3.1= 2023.q3.2= 2023.q3.3= 2023.q3.4= 2023.q3.5CVSS 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 Lifer Portal/DXP versionAccess the Lifer Control Panel > Configuration > Server Administration > Product Information, or inspect the portal-ext.properties or OSGi manifest files for the exact version numberAffected if The installed version is >= 7.4.3.18 and < 7.4.3.102 for Lifer Portal, or exactly 7.4, 2023.q3.0, 2023.q3.1, 2023.q3.2, 2023.q3.3, 2023.q3.4, or 2023.q3.5 for DXP
-
Verify Document and Media widget is accessibleNavigate to the Lifer Control Panel > Apps > Widgets and confirm the Document and Media portlet is installed; check permissions to ensure authenticated users can access itAffected if The Document and Media widget is deployed and enabled for authenticated users in the environment
-
Inspect existing documents for suspicious titlesIn the Document and Media library, review document titles for unescaped HTML/script tags such as <script>, javascript:, or event handlers like onload/onerrorAffected if Any documents exist with script tags or HTML markup embedded in their Title field that would execute when viewed
The environment is affected if the Lifer version falls within the listed vulnerable ranges AND the Document and Media widget is accessible to authenticated users, allowing them to create or modify document titles.
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.102
Apply vendor-provided patches (patch 6 for DXP 2023.Q3, update 92 for 7.4) or implement output encoding/sanitization on the Title field before rendering.
Lifera Portal 7.4.3.102+ / Lifera DXP 2023.Q3 Patch 6+ / Lifera DXP 7.4 Update 93+
- Upgrade Liferay Portal from versions 7.4.3.18 through 7.4.3.101 to version 7.4.3.102 or later
- For Lifera DXP 2023.Q3, apply patch 6 or later to address the vulnerability
- For Lifera DXP 7.4, upgrade from update 18-92 to update 93 or later
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-2023-47795 — 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-47795 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