How severe is GHSA-v53g-736w-mgw4?

No CVSS score has been assigned to GHSA-v53g-736w-mgw4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v53g-736w-mgw4?

GHSA-v53g-736w-mgw4 affects the following packages: com.liferay:com.liferay.organizations.item.selector.web (Maven). Ecosystems affected: Maven.

How do I fix GHSA-v53g-736w-mgw4?

Update com.liferay:com.liferay.organizations.item.selector.web to 4.0.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v53g-736w-mgw4 is resolved across your whole dependency graph.

How do I detect GHSA-v53g-736w-mgw4 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay:com.liferay.organizations.item.selector.web. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-v53g-736w-mgw4 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-v53g-736w-mgw4?

O3 pinpoints whether GHSA-v53g-736w-mgw4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-v53g-736w-mgw4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-v53g-736w-mgw4 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 type of vulnerability is GHSA-v53g-736w-mgw4?

GHSA-v53g-736w-mgw4 is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-v53g-736w-mgw4 published, and has it been updated?

GHSA-v53g-736w-mgw4 was published on September 12, 2025 and was last updated on December 20, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

GHSA-v53g-736w-mgw4

Fix: liferay/liferay-portal@730b084

GHSA-v53g-736w-mgw4 is a CWE-862 vulnerability in com.liferay:com.liferay.organizations.item.selector.web. O3 Security confirms whether GHSA-v53g-736w-mgw4 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Liferay Portal's Organization Selector exposes organization data to remote authenticated users

Also known asCVE-2025-43788

Published

Sep 12, 2025

Updated

Dec 20, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 20, 2025 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

☕com.liferay:com.liferay.organizations.item.selector.web

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

The Organization Selector in Liferay Portal 7.4.0 through 7.4.3.124, and Liferay DXP 2024.Q1.1 through 2024.Q1.12 and 7.4 update 81 through update 85 does not check user permission, which allows remote authenticated users to obtain a list of all organizations.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay:com.liferay.organizations.item.selector.web`	≥ 4.0.2&&< 4.0.22	4.0.22

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.organizations.item.selector.web. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update com.liferay:com.liferay.organizations.item.selector.web to 4.0.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v53g-736w-mgw4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-v53g-736w-mgw4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-v53g-736w-mgw4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-v53g-736w-mgw4 in your dependencies?

O3 detects GHSA-v53g-736w-mgw4 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works