CVE-2022-42128
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 · uneditedThe Hypermedia REST APIs module in Liferay Portal 7.4.1 through 7.4.3.4, and Liferay DXP 7.4 GA does not properly check permissions, which allows remote attackers to obtain a WikiNode object via the WikiNodeResource.getSiteWikiNodeByExternalReferenceCode API.
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 confidenceThe Hypermedia REST APIs module in Lifter Portal 7.4.1-7.4.3.4 and Lifer DXP 7.4 GA fails to enforce proper authorization checks on the WikiNodeResource.getSiteWikiNodeByExternalReferenceCode API endpoint, allowing remote attackers to retrieve WikiNode objects without authentication or appropriate permissions.
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.1, < 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 Lifer product and versionCheck the Lifer Portal or DXP installation by reviewing the bundle or checking the Lifer Home control panel for the exact version numberAffected if Version is 7.4.1 through 7.4.3.4 for Portal, or 7.4 GA for DXP
-
Confirm the Hypermedia REST APIs module is enabledAccess the Lifer control panel and navigate to System Settings > API > GraphQL/REST APIs, or inspect the OSGi console for com_lifer_rest_api module activationAffected if The REST API module is active and exposed externally
-
Verify external access to REST API endpointsTest network connectivity to the /o/api endpoints (such as /o/headless-delivery-user-defined-entities or /api/jsonws endpoints) from an untrusted networkAffected if The REST APIs are reachable from external networks without authentication requirements
-
Test unauthorized WikiNode accessAttempt a GET request to the WikiNode resource endpoint (such as /o/headless-delivery-user-defined-entities/v1.0/sites/{siteId}/wiki-nodes/{externalReferenceCode}) without providing valid authentication credentialsAffected if The endpoint returns WikiNode data without requiring authentication or returns unauthorized results that indicate broken access control
If Lifer Portal/DXP version 7.4.1 through 7.4.3.4 is running and the REST API module is exposed externally without network-level access controls, the environment is vulnerable to this authorization bypass.
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.
From vendor data7.4.3.5
Apply Lifer's security patch or upgrade to a patched version of Lifer Portal/DXP. Until patched, restrict external access to REST API endpoints via network-level controls or API gateway filtering.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42128 — 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-42128 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