dbcve.org
DxpApplication · Liferay

CVE-2022-28982

MEDIUM · 6.1 CVSS v3.1 Published 2022-09-22
Fix available
A fix is available. Upgrade to 7.4.3.4 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
A cross-site scripting (XSS) vulnerability in Liferay Portal v7.3.3 through v7.4.2 and Liferay DXP v7.3 before service pack 3 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the name of a tag.

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

A cross-site scripting (XSS) vulnerability in Lifer Portal v7.3.3 through v7.4.2 and Lifer DXP v7.3 before service pack 3 allows attackers to inject malicious scripts into the name parameter of a tag, which is then rendered without proper sanitization, enabling execution of arbitrary web scripts or HTML in the context of user sessions.

MitigationUpgrade to Lifer Portal v7.4.3 or later, or apply Lifer DXP v7.3 service pack 3 or later to address the insufficient input validation on tag names.

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
DxpApplication
Affected:= 7.3
Liferay PortalApplication
Affected:>= 7.3.3, < 7.4.3.4

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 Lifer product and version
    Locate the Lifer installation and check the version information, typically found in the product's about page, version file, or control panel. For Lifer Portal, this is often accessible via the Control Panel > Configuration > Server Administration > Resources. For Lifer DXP, check the Digital Experience Platform version details.
    Affected if The installed version is Lifer Portal between 7.3.3 and 7.4.3.4 inclusive, or Lifer DXP version 7.3 without service pack 3 applied.
  2. Determine if running Lifer Portal and exact version
    Confirm whether the installation is Lifer Portal (not DXP) and obtain the precise minor/patch version number.
    Affected if Running Lifer Portal version 7.3.3, 7.3.4, 7.3.5, 7.4.0, 7.4.1, 7.4.2, or any version >= 7.3.3 but < 7.4.3.4.
  3. Determine if running Lifer DXP and service pack level
    For Lifer DXP 7.3 installations, check if Service Pack 3 has been applied. This information is typically visible in the Server Administration panel or release information.
    Affected if Running Lifer DXP 7.3 without Service Pack 3 installed.
  4. Identify tag functionality usage
    Review application configuration or examine requests to tag-related endpoints where the name parameter can be supplied. This may involve reviewing tag management interfaces or API endpoints that handle tag name inputs.
    Affected if The tag name parameter can be supplied by users without proper sanitization, and the application renders this value in web pages.

You are affected if you are running Lifer Portal versions 7.3.3 through 7.4.3.4, or Lifer DXP 7.3 without Service Pack 3, and your users have access to create or modify tag names that get rendered in the UI.

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.4 or later
Fixed in 7.4.3.4
Interim mitigation

Upgrade to Lifer Portal v7.4.3 or later, or apply Lifer DXP v7.3 service pack 3 or later to address the insufficient input validation on tag names.

Recommended fix High confidence

LXP Portal 7.4.3.4+ or LXP DXP 7.3 Service Pack 3+

  1. 1. Back up your current LXP Portal/DXP installation and database
  2. 2. Review Liferaries upgrade documentation for your version at https://help.liferays.com/
  3. 3. For LXP Portal: upgrade to version 7.4.3.4 or later
  4. 4. For LXP DXP: upgrade to service pack 3 or later
  5. 5. After upgrade, verify the tag library functionality works correctly
  6. 6. Test that XSS payloads in tag names are no longer executed
Caveat Major upgrades between 7.3 and 7.4 may have breaking changes; review Liferaries migration guide and deprecation notices before upgrading

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

Fix this in Dxp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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