dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2023-44311

MEDIUM · 6.1 CVSS v3.1 Published 2023-10-17
Fix available
A fix is available. Upgrade to 7.4.3.90 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
Multiple reflected cross-site scripting (XSS) vulnerabilities in the Plugin for OAuth 2.0 module's OAuth2ProviderApplicationRedirect class in Liferay Portal 7.4.3.41 through 7.4.3.89, and Liferay DXP 7.4 update 41 through update 89 allow remote attackers to inject arbitrary web script or HTML via the (1) code, or (2) error parameter. This issue is caused by an incomplete fix in CVE-2023-33941.

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 Liferel's OAuth 2.0 plugin's OAuth2ProviderApplicationRedirect class allows injection via the 'code' or 'error' parameters during OAuth authentication redirects. This is an incomplete fix from CVE-2023-33941, affecting Portal 7.4.3.41-89 and DXP 7.4 update 41-89.

MitigationUpgrade to Liferel 7.4.3.90 or later, or apply the corresponding security patch to properly sanitize the 'code' and 'error' parameters in OAuth redirects.

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:= 7.4
Liferay PortalApplication
Affected:>= 7.4.3.41, < 7.4.3.90

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. Check Lifer Portal/DXP version
    Access the Lifer Control Panel > Configuration > Server Administration > Overview, or inspect the portal-version property in portal-ext.properties or the deployed lifer-portal-*.war file manifest
    Affected if The installed version is between 7.4.3.41 and 7.4.3.89 inclusive, or the DXP version is 7.4 without a specific update number in that range
  2. Verify OAuth 2.0 authentication is enabled
    Navigate to Control Panel > Configuration > OAuth, or check for OAuth2ProviderApplicationRedirect class in the deployed modules (under osgi/marketplace/* or the application war)
    Affected if OAuth 2.0 authorization server or any OAuth provider is configured in the Lifer instance
  3. Inspect OAuth redirect configuration
    Check the OAuth2ProviderApplicationRedirect.java source if accessible, or examine the OAuth provider settings in the Control Panel for the redirect endpoint that handles 'code' and 'error' parameters
    Affected if The OAuth redirect handler exists and processes the 'code' or 'error' query parameters without visible sanitization in the configuration or logs
  4. Confirm plugin patch state (optional)
    Review the applied hotfixes via Lifer Fix Pack Manager or check the bundle.info file in the osgi/state directory for security patch indicators
    Affected if No patch for CVE-2023-44311 or CVE-2023-33941 is listed as applied, and the version remains in the vulnerable range

The environment is affected if Lifer Portal/DXP version 7.4.3.41 through 7.4.3.89 is running and OAuth 2.0 authentication is enabled, with no corresponding security patch applied.

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.90 or later
Fixed in 7.4.3.90
Interim mitigation

Upgrade to Liferel 7.4.3.90 or later, or apply the corresponding security patch to properly sanitize the 'code' and 'error' parameters in OAuth redirects.

Recommended fix High confidence

Liferax Portal 7.4.3.90 or later / Liferax DXP 7.4 Update 90 or later

  1. Upgrade Liferax Portal from any version >= 7.4.3.41 and < 7.4.3.90 to version 7.4.3.90 or later
  2. If using Liferax DXP 7.4, upgrade from update 41 through update 89 to update 90 or later
  3. After upgrading, verify the OAuth2ProviderApplicationRedirect class properly encodes the code and error parameters to prevent XSS attacks

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

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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