How severe is CVE-2022-42128?

No CVSS score has been assigned to CVE-2022-42128 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2022-42128?

CVE-2022-42128 affects the following packages: liferay (Bitnami). Ecosystems affected: Bitnami.

How do I fix CVE-2022-42128?

The records we use list no patched version of liferay for CVE-2022-42128. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2022-42128 in my Bitnami dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for liferay, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-42128 if there is no patch (or I can't update yet)?

Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Is CVE-2022-42128 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-42128 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-42128?

CVE-2022-42128 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 55th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-42128?

CVE-2022-42128 is classified as Incorrect Default Permissions (CWE-276). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-42128 published, and has it been updated?

CVE-2022-42128 was published on January 31, 2024 and was last updated on February 19, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Bitnami

Not in CISA KEV

CVE-2022-42128 — liferay

CVE-2022-42128 is a Incorrect Default Permissions vulnerability in liferay. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asGHSA-wgqm-qp44-cg6x

Published

Jan 31, 2024

Updated

Feb 19, 2024

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-42128.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk+0.05%

Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

📦liferay

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Bitnami packages — download data is not available via public APIs for these ecosystems.

Description

The 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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦Bitnami	`liferay`	≥ 7.4.0	No fix

Affected Products

2 products · 2 configurations

Application

digital experience platformliferay

1 version

7.4

Application

liferay portalliferay

≥ 7.4.1 && < 7.4.3.5

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for liferay, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of liferay for CVE-2022-42128. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-42128 in your dependencies?

Find it across Bitnami, including transitive dependencies.

Scan my dependencies How O3 SCA works