CVE-2022-42110
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 · uneditedA Cross-site scripting (XSS) vulnerability in the Announcements module in Liferay Portal 7.1.0 through 7.4.2, and Liferay DXP 7.1 before fix pack 27, 7.2 before fix pack 17, and 7.3 before service pack 3 allows remote attackers to inject arbitrary web script or HTML.
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 confidenceA stored Cross-site scripting (XSS) vulnerability exists in Lermat Portal and DXP's Announcements module. The vulnerability allows remote attackers to inject arbitrary web script or HTML through malicious content submitted via the Announcements module, which is then rendered without proper output encoding when viewed by other users.
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.1.0, <= 7.4.2= 7.1= 7.2= 7.3CVSS 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.
-
Determine installed L Portal or DXP versionAccess the Control Panel > Configuration > Server Administration > Product Information, or check the portal-ext.properties file for the version property. Alternatively, examine the WAR file or Docker image tag if deployed in containers.Affected if The installed version falls within 7.1.0 to 7.4.2 for L Portal, or is exactly 7.1, 7.2, or 7.3 for DXP.
-
Locate the Announcements moduleNavigate to Control Panel > Apps > App Manager and search for 'Announcements' or check for the com_liferays Announcements portlet in the web applications. On the running instance, access the Announcements portlet typically found in the User Dashboard or via the Add Application menu.Affected if The Announcements module or portlet is present and deployed on the system.
-
Check if Announcements portlet is accessible to usersIn Control Panel > Users > Roles, verify which roles have permissions to the Announcements portlet (portlet ID: 1_WAR_Announcementsportlet). Check if authenticated users or non-admin users have 'Add Entry' or 'Add to Page' permissions.Affected if Regular authenticated users or guest users have permission to create or add Announcements entries.
-
Inspect Announcements entries for unsanitized contentAs a user with Announcements access, view existing Announcements entries. Check the HTML source of the Announcements display page using browser developer tools to see if HTML or script tags are being rendered as raw text or as executed code.Affected if HTML script tags or JavaScript code entered in the Announcements content field renders and executes in the browser rather than being displayed as plain text.
Your environment is affected if you run a vulnerable L Portal (7.1.0-7.4.2) or DXP (7.1/7.2/7.3) version AND have the Announcements module enabled with permissions that allow users to create entries.
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 · scopedApply the relevant fix packs (Lermat Portal 7.4.3+, DXP FP27/FP17/SP3 or later) which include input validation and output encoding fixes for the Announcements module. Until patched, restrict access to the Announcements module functionality.
Lifer DXP: Fix Pack 27+ (7.1), Fix Pack 17+ (7.2), Service Pack 3+ (7.3) | Lifer Portal: 7.4.3 or later
- 1. Identify the currently installed Lifer Portal or DXP version using the Lifer Control Panel or server logs
- 2. For Lifer DXP 7.1: Apply Fix Pack 27 or later
- 3. For Lifer DXP 7.2: Apply Fix Pack 17 or later
- 4. For Lifer DXP 7.3: Apply Service Pack 3 or later
- 5. For Lifer Portal 7.1.0-7.4.2: Upgrade to Lifer Portal 7.4.3 or later
- 6. After applying the fix, verify the Announcements module functionality
- 7. Test that the XSS vulnerability is remediated by attempting to inject script content in the Announcements portlet
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2022-42110 — 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-42110 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