How severe is GHSA-477q-x55m-j38g?

No CVSS score has been assigned to GHSA-477q-x55m-j38g yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-477q-x55m-j38g?

GHSA-477q-x55m-j38g affects the following packages: com.liferay:com.liferay.object.service (Maven). Ecosystems affected: Maven.

How do I fix GHSA-477q-x55m-j38g?

Update com.liferay:com.liferay.object.service to 1.0.208 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-477q-x55m-j38g is resolved across your whole dependency graph.

How do I detect GHSA-477q-x55m-j38g in my Maven dependencies?

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

How do I mitigate GHSA-477q-x55m-j38g if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is GHSA-477q-x55m-j38g actively exploited in the wild?

No public exploit code has been indexed for GHSA-477q-x55m-j38g 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 GHSA-477q-x55m-j38g?

GHSA-477q-x55m-j38g has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 9th 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 GHSA-477q-x55m-j38g?

GHSA-477q-x55m-j38g is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-477q-x55m-j38g published, and has it been updated?

GHSA-477q-x55m-j38g was published on September 9, 2025 and was last updated on September 10, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Liferay Portal is vulnerable to SSRF through custom…

Exploitation Status

No confirmed exploitation observed yet

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 GHSA-477q-x55m-j38g.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs9th percentile — riskier than 9% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕com.liferay:com.liferay.object.service

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

Description

A server-side request forgery (SSRF) vulnerability exist in the Liferay Portal 7.4.0 through 7.4.3.131, and Liferay DXP 2024.Q4.0 through 2024.Q4.7, 2024.Q3.0 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13 and 2024.Q1.1 through 2024.Q1.20 that affects custom object attachment fields. This flaw allows an attacker to manipulate the application into making unauthorized requests to other instances, creating new object entries that link to external resources.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay:com.liferay.object.service`	all versions	1.0.208`com.liferay:com.liferay.object.service:1.0.208`

Affected Products

2 products · 5 configurations

Application

digital experience platformliferay

≥ 2024.q4.0 && ≤ 2024.q4.7

range

Application

liferay portalliferay

≥ 7.4.0 && < 7.4.3.132

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay:com.liferay.object.service, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay:com.liferay.object.service to 1.0.208 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-477q-x55m-j38g is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

A server-side request forgery (SSRF) vulnerability exist in the Liferay Portal 7.4.0 through 7.4.3.131, and Liferay DXP 2024.Q4.0 through 2024.Q4.7, 2024.Q3.0 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13 and 2024.Q1.1 through 2024.Q1.20 that affects custom object attachment fields. This flaw allows an attacker to manipulate the application into making unauthorized requests to other instances, creating new object entries that link to external resources.

O3 Security · Impact-Aware SCA

Is GHSA-477q-x55m-j38g in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

Liferay Portal is vulnerable to SSRF through custom object attachment fieldsGHSA-477q-x55m-j38g