CVE-2022-28980
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 · uneditedMultiple cross-site scripting (XSS) vulnerabilities in Liferay Portal v7.4.3.4 and Liferay DXP v7.4 GA allows attackers to execute arbitrary web scripts or HTML via parameters with the filter_ prefix.
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 · moderate confidenceLiferay Portal/DXP 7.4 contains multiple reflected cross-site scripting vulnerabilities where user-supplied input in parameters prefixed with 'filter_' is not properly sanitized before being rendered in web pages. An attacker can craft malicious URLs containing JavaScript or HTML payloads in filter_ parameters to execute in the context of authenticated user sessions.
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.4< 7.4.3.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Lifer Portal/DXP versionAccess the Lifer Control Panel, navigate to Configuration > Server Administration > Product Information, or query the database table Release_ with releaseType='eee' to retrieve the version. Alternatively, check the portal-ext.properties file or the OSGi bundle metadata for version information.Affected if The version is Lifer DXP 7.4 (any build) or Lifer Portal with version lower than 7.4.3.5.
-
Verify presence of filter_ prefixed parametersReview application URL parameters and search application logs, proxy logs, or use a web vulnerability scanner to identify any endpoints accepting parameters that begin with 'filter_' (such as filter_date, filter_status, filter_name).Affected if The application accepts and processes parameters with the 'filter_' prefix without validation.
-
Inspect output encoding for filter_ parametersCapture a response from an endpoint that echoes back a filter_ parameter value. Examine the HTTP response in a browser developer tool or use curl to inspect whether the filter_ value is returned without HTML encoding (e.g., compare <script>alert(1)</script> in the parameter vs. in the response).Affected if The filter_ parameter value is reflected in the response as raw, unencoded text, enabling script injection.
-
Confirm authentication requirementsReview access logs or authentication configuration to determine whether endpoints using filter_ parameters are accessible only to authenticated users.Affected if The vulnerable filter_ endpoints are accessible to authenticated users, meaning the XSS payload can execute in an authenticated session context.
A user is affected if they run Lifer Portal below 7.4.3.5 or any Lifer DXP 7.4 version, AND their application accepts filter_ prefixed parameters that are reflected unencoded in web responses to authenticated 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.5
Apply the latest Liferay security patches or upgrade to a version beyond v7.4.3.4 that addresses this vulnerability. Additionally, implement output encoding and input validation for all parameters starting with 'filter_' as a defense-in-depth measure.
Lifera Portal 7.4.3.5 or Lifera DXP 7.4 Fix Pack 5
- 1. Back up your current Liferay Portal/DXP installation and database before proceeding
- 2. Download Liferay Portal 7.4.3.5 or Liferay DXP 7.4 Fix Pack 5 from the official Livery releases
- 3. Stop the L application server running the affected installation
- 4. Install the upgrade by deploying the new Lifer version following L standard upgrade procedures
- 5. Run any required database upgrade scripts for the new version
- 6. Start the application server and verify the instance starts successfully
- 7. Test that the fix addresses the XSS vulnerability by validating that parameters with the filter_ prefix are now properly sanitized
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28980 — 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-2022-28980 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