CVE-2025-62258: Liferay Portal · Cross-Site Request Forgery (CSRF)
Affects Liferay PortalSource CVE Database V5
Not known to be exploited · CVSS 7.0 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% 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:A/VC:L/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavencom.liferay.portal/portalpkg:maven/com.liferay.portal/portalOther threats | Affected
| 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 and updates from Liferay as soon as they become available to address CVE-2025-62258. 2. Implement robust anti-CSRF tokens in all Headless API endpoints to validate the origin and intent of requests. 3. Restrict access to the Headless API by enforcing strict network-level controls such as IP whitelisting and VPN-only access. 4. Employ Content Security Policy (CSP) headers and SameSite cookie attributes to reduce the risk of CSRF via browser-based attacks. 5. Conduct user awareness training to recognize and avoid phishing attempts that could trigger malicious requests. 6. Review and minimize user privileges to limit the potential impact of compromised accounts. 7. Monitor logs for unusual API activity that could indicate exploitation attempts. 8. Consider deploying Web Application Firewalls (WAF) with custom rules to detect and block suspicious Headless API calls. 9. Regularly audit and test the security posture of Liferay deployments, including penetration testing focused on API security.
Description
CSRF vulnerability in Headless API in Liferay Portal 7.4.0 through 7.4.3.107, 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 allows remote attackers to execute any Headless API via the `endpoint` parameter.