How severe is GHSA-pw86-qvx9-34r7?

No CVSS score has been assigned to GHSA-pw86-qvx9-34r7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pw86-qvx9-34r7?

GHSA-pw86-qvx9-34r7 affects the following packages: com.liferay:com.liferay.portal.security.audit.web (Maven), com.liferay:com.liferay.portal.security.audit.storage.service (Maven). Ecosystems affected: Maven.

How do I fix GHSA-pw86-qvx9-34r7?

Update com.liferay:com.liferay.portal.security.audit.web to 5.0.33 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pw86-qvx9-34r7 is resolved across your whole dependency graph.

How do I detect GHSA-pw86-qvx9-34r7 in my Maven dependencies?

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

How do I mitigate GHSA-pw86-qvx9-34r7 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-pw86-qvx9-34r7?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pw86-qvx9-34r7 can be triaged on real exposure rather than presence alone.

Is GHSA-pw86-qvx9-34r7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-pw86-qvx9-34r7 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-pw86-qvx9-34r7?

GHSA-pw86-qvx9-34r7 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 19th 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-pw86-qvx9-34r7?

GHSA-pw86-qvx9-34r7 is classified as CWE-639 (CWE-639). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-pw86-qvx9-34r7 published, and has it been updated?

GHSA-pw86-qvx9-34r7 was published on September 30, 2025 and was last updated on December 17, 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-pw86-qvx9-34r7 — com.liferay.portal.securi…

Fix: liferay/liferay-portal@a14427e

GHSA-pw86-qvx9-34r7 is a CWE-639 vulnerability in com.liferay:com.liferay.portal.security.audit.web. A fix is available for com.liferay:com.liferay.portal.security.audit.web — see the affected versions and patch details below.

Liferay Portal Vulnerable to IDOR via audit events

Also known asCVE-2025-43827

Published

Sep 30, 2025

Updated

Dec 17, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

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-pw86-qvx9-34r7.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs19th percentile — riskier than 19% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

☕com.liferay:com.liferay.portal.security.audit.web☕com.liferay:com.liferay.portal.security.audit.storage.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

Insecure Direct Object Reference (IDOR) vulnerability with audit events in Liferay Portal 7.4.0 through 7.4.3.117, and older unsupported versions, and Liferay DXP 2024.Q1.1 through 2024.Q1.5, 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.10, 7.4 GA through update 92, and older unsupported versions allows remote authenticated users to from one virtual instance to view the audit events from a different virtual instance via the _com_liferay_portal_security_audit_web_portlet_AuditPortlet_auditEventId parameter.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay:com.liferay.portal.security.audit.web`	≥ 5.0.1&&< 5.0.33	5.0.33`com.liferay:com.liferay.portal.security.audit.web:5.0.33`
☕Maven	`com.liferay:com.liferay.portal.security.audit.storage.service`	≥ 6.0.4&&< 6.0.41	6.0.41`com.liferay:com.liferay.portal.security.audit.storage.service:6.0.41`

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.portal.security.audit.web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay:com.liferay.portal.security.audit.web to 5.0.33 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pw86-qvx9-34r7 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pw86-qvx9-34r7 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-pw86-qvx9-34r7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Insecure Direct Object Reference (IDOR) vulnerability with audit events in Liferay Portal 7.4.0 through 7.4.3.117, and older unsupported versions, and Liferay DXP 2024.Q1.1 through 2024.Q1.5, 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.10, 7.4 GA through update 92, and older unsupported versions allows remote authenticated users to from one virtual instance to view the audit events from a different virtual instance via the `_com_liferay_portal_security_audit_web_portlet_AuditPortlet_auditEventId` parameter.

O3 Security · Impact-Aware SCA

Is GHSA-pw86-qvx9-34r7 in your dependencies?

O3 Security finds GHSA-pw86-qvx9-34r7 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works