Skip to main content
VulnerabilityPublished

CVE-2025-62259: Liferay Portal · Incorrect Authorization

Affects Liferay PortalSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Mavencom.liferay.portal/portalpkg:maven/com.liferay.portal/portalOther threatsAffected
  • =7.4.0
  • <=7.4.3.109
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Apply official patches from Liferay as soon as they become available for all affected versions.
  2. Until patches are released, implement network-level restrictions to limit API access to trusted IP ranges or VPNs.
  3. Configure web application firewalls (WAFs) to detect and block unauthorized API calls that attempt to modify content without verified email status.
  4. Review and harden API access controls by enforcing email verification or additional authentication mechanisms before allowing content edits.
  5. Monitor logs for unusual API activity, especially from unauthenticated sources, and establish alerting for suspicious content modification attempts.
  6. Conduct internal audits of Liferay configurations and user verification workflows to ensure no bypasses exist.
  7. Educate administrators and developers about the vulnerability and encourage prompt remediation.
  8. Consider isolating legacy or unsupported Liferay instances from public networks until they can be upgraded or patched.

Description

Liferay Portal 7.4.0 through 7.4.3.109, and older unsupported versions, and Liferay DXP 2023.Q3.1 through 2023.Q3.4, 7.4 GA through update 92, 7.3 GA through update 35, and older unsupported versions does not limit access to APIs before a user has verified their email address, which allows remote users to access and edit content via the API.

References

Community reviews

Loading reviews…