dbcve.org
Liferay PortalApplication · Liferay

CVE-2023-40191

MEDIUM · 6.1 CVSS v3.1 Published 2024-02-21
Fix available
A fix is available. Upgrade to 7.4.3.98 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 in the instance settings for Accounts in Liferay Portal 7.4.3.44 through 7.4.3.97, and Liferay DXP 2023.Q3 before patch 6, and 7.4 update 44 through 92 allows remote attackers to inject arbitrary web script or HTML via a crafted payload injected into the “Blocked Email Domains” 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 confidence

Reflected XSS vulnerability in Liferay Portal 7.4.3.44-7.4.3.97 and DXP 2023.Q3 before patch 6 allows remote attackers to inject arbitrary web script or HTML via the 'Blocked Email Domains' text field in Account instance settings.

MitigationApply the relevant vendor patch (Q3 patch 6 or later updates) and implement proper input sanitization/validation on the Blocked Email Domains field to prevent script injection.

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.44, < 7.4.3.98
Digital Experience PlatformApplication
Affected:= 7.4= 2023.q3.0= 2023.q3.1= 2023.q3.2= 2023.q3.3= 2023.q3.4= 2023.q3.5

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 Lifford Portal or DXP version
    Check the installed Lifford version via the Control Panel or by examining the liferay-portal.properties or manifest files in the deployment
    Affected if Version is 7.4.3.44 through 7.4.3.97 for Portal, or 7.4 / 2023.Q3.0 through 2023.Q3.5 for DXP
  2. Confirm Account Management is enabled
    Navigate to Control Panel > Account Settings and verify the Account Instances section is accessible
    Affected if Account management functionality is available and the instance settings can be modified
  3. Locate the Blocked Email Domains field
    Navigate to Account > Account Settings > General (or Instances tab depending on version) and locate the Blocked Email Domains text input field
    Affected if The Blocked Email Domains field exists and accepts user input in the Account instance settings
  4. Check for existing injected content
    Review the current value of the Blocked Email Domains field for any unexpected script tags, HTML elements, or suspicious domain entries
    Affected if The field contains unexpected HTML tags, JavaScript, or suspicious domain patterns not explicitly added by administrators

A user is affected if they are running Lifford Portal 7.4.3.44-7.4.3.97 or DXP 7.4/2023.Q3.0-2023.Q3.5 and the Blocked Email Domains field in Account instance settings contains or is vulnerable to injected script or HTML content.

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.98 or later
Fixed in 7.4.3.98
Interim mitigation

Apply the relevant vendor patch (Q3 patch 6 or later updates) and implement proper input sanitization/validation on the Blocked Email Domains field to prevent script injection.

Recommended fix High confidence

LPortal 7.4.3.98+ / DXP 7.4 update 92+ / DXP 2023.q3 patch 6+

  1. Backup the current Liferay Portal/DXP database and installation
  2. Stop the Liferay Portal/DXP service
  3. For Liferay Portal: Upgrade to version 7.4.3.98 or later
  4. For Liferay DXP 7.4: Upgrade to update 92 or later
  5. For Liferay DXP 2023.q3: Apply patch 6 or later
  6. Verify the upgrade was successful by checking the Lifer version
  7. Restart the Lifer service
  8. Log in to instance settings and confirm the 'Blocked Email Domains' field now properly sanitizes input

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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