dbcve.org
Liferay PortalApplication · Liferay

CVE-2023-47797

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-17
Fix available
A fix is available. Upgrade to after 7.4.3.95 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Reflected cross-site scripting (XSS) vulnerability on a content page’s edit page in Liferay Portal 7.4.3.94 through 7.4.3.95 allows remote attackers to inject arbitrary web script or HTML via the `p_l_back_url_title` parameter.

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

Reflected XSS vulnerability in Liferay Portal 7.4.3.94-7.4.3.95 allows remote attackers to inject arbitrary web script or HTML via the p_l_back_url_title parameter on content page edit pages.

MitigationUpdate Liferay Portal to version 7.4.3.96 or later, which contains the patched version. As a compensating control, implement strict input validation and output encoding on the p_l_back_url_title parameter.

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
Liferay PortalApplication
Affected:>= 7.4.3.94, <= 7.4.3.95

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 the installed Lifer Portal version
    Access the Control Panel, then navigate to Configuration > Server Administration > Server, or use the Gogo shell command 'system:property liferay.version' to retrieve the exact version number
    Affected if The installed version is 7.4.3.94 or 7.4.3.95 (the only affected versions in the specified range)
  2. Confirm the Lifer Portal build number
    In Server Administration, locate the Build number or Build date field. Compare this against the known affected builds for versions 7.4.3.94 and 7.4.3.95
    Affected if The build number matches those corresponding to the affected 7.4.3.94-7.4.3.95 versions
  3. Determine if content page editing is accessible
    Log in with administrative or content authoring privileges and verify access to the Site Builder > Content Pages section, or attempt to access a content page in edit mode via the URL structure that includes page editing parameters
    Affected if Content page editing functionality is enabled and the user can access content page edit pages
  4. Verify the vulnerable parameter is present in the environment
    Inspect the HTML source or form parameters on content page edit screens, specifically looking for the p_l_back_url_title parameter in rendered forms or network requests when loading content page edit pages
    Affected if The p_l_back_url_title parameter is found in content page edit page requests or forms

The environment is affected only if the installed Lifer Portal version is exactly 7.4.3.94 or 7.4.3.95 AND content page editing with the p_l_back_url_title parameter is accessible in the environment.

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 a release after 7.4.3.95
Interim mitigation

Update Liferay Portal to version 7.4.3.96 or later, which contains the patched version. As a compensating control, implement strict input validation and output encoding on the p_l_back_url_title parameter.

Recommended fix Moderate confidence

Liferay Portal 7.4.3.96 or later

  1. 1. Identify the current Liferay Portal version by checking the Lifera DXP or Liferay Portal installation
  2. 2. Download and install Liferay Portal 7.4.3.96 or later from the official Liferay downloads page (https://www.liferay.com/downloads)
  3. 3. Before upgrading, perform a full backup of the existing Liferay Portal database and documents library
  4. 4. Test the upgrade in a non-production environment to verify compatibility
  5. 5. Deploy the upgraded version to production environment
  6. 6. Verify that the p_l_back_url_title parameter is properly sanitized by testing the content page edit functionality
Caveat Minor upgrade within 7.4.x branch - review Liferay release notes for any deprecation notices

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

Fix this in Liferay Portal Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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