CVE-2023-44310
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 Page Tree menu Liferay Portal 7.3.6 through 7.4.3.78, and Liferay DXP 7.3 fix pack 1 through update 23, and 7.4 before update 79 allows remote attackers to inject arbitrary web script or HTML via a crafted payload injected into page'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 confidenceStored cross-site scripting (XSS) vulnerability in Lifer Portal/DXP's Page Tree menu allows attackers to inject malicious JavaScript or HTML into the page 'Name' field. The payload is stored and executed when other users view the affected page tree, enabling session hijacking or defacement.
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.1= 7.4>= 7.3.6, < 7.4.3.49CVSS 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 the Lifer Portal/DXP versionAccess the Control Panel > Configuration > Server Administration > Product Information, or inspect the portal-impl.jar bundle version, or query the database for the release table version entryAffected if The installed version is 7.1.x, 7.4.x prior to update 79, or falls within 7.3.6 through 7.4.3.48
-
Verify access to the Page Tree menuLog in as an administrator and navigate to Site Builder > Pages, then locate the Page Tree panel typically found in the left navigation of the Pages admin interfaceAffected if The Page Tree menu interface is accessible and visible in the admin console
-
Inspect page names in the Page Tree for script tagsOpen the Page Tree menu and manually review each page entry for suspicious characters such as <script>, javascript:, onerror=, or other HTML/script tags in the Name field; alternatively, query the layout table in the database for Name values containing HTML tagsAffected if Any page Name field in the tree contains unescaped HTML or JavaScript syntax
-
Test for XSS by viewing the Page Tree as a non-admin userCreate a test user without admin privileges, have them access the same site and navigate to the Pages section with Page Tree visible, then monitor if script execution occurs in their browserAffected if Malicious scripts stored in page Names execute when viewed by other users
A user is affected if their Lifer Portal/DXP version falls within 7.3.6 to 7.4.3.48 or matches 7.1.x/7.4.x, AND the Page Tree menu is in use, AND page Name fields contain unsanitized HTML/JavaScript that executes when viewed by other users.
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.49
Upgrade Lifer DXP to version 7.4 update 79 or later, or apply the appropriate patch for 7.3.x versions to ensure proper input sanitization in the Page Tree menu Name field.
Lifer Portal 7.4.3.78+ or DXP 7.4 Update 79+
- 1. Identify the current Liferay installation version (Portal or DXP)
- 2. For LPortal installations, upgrade to version 7.4.3.78 or later
- 3. For DXP 7.4 installations, apply Liferay DXP 7.4 Update 79 or later
- 4. For DXP 7.3 installations, apply Lifer 7.3 Fix Pack 24 or later
- 5. After upgrading, verify the patch was applied by checking the Lifer Version panel under Control Panel > Configuration > Server Administration
- 6. Test the Page Tree menu functionality to confirm the fix works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-44310 — 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-44310 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