# CVE-2025-3639: Liferay Portal Login Bypass Vulnerability > Authenticated users can bypass Multi-Factor Authentication by changing the HTTP method from POST to GET during login. - **Severity:** Low 2.0 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:P/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 18 Aug 2025 - **Updated:** 18 Aug 2025 - **Also known as:** GHSA-g4wg-mpfg-x2q6 ## What is CVE-2025-3639? CVE-2025-3639 is a low-severity authentication bypass vulnerability in Liferay DXP, published on 18 Aug 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link. ### Official description Liferay Portal 7.3.0 through 7.4.3.132, and Liferay DXP 2025.Q1 through 2025.Q1.6, 2024.Q4.0 through 2024.Q4.7, 2024.Q3.1 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.15, 7.4 GA through update 92 and 7.3 GA through update 36 allows unauthenticated users with valid credentials to bypass the login process by changing the POST method to GET, once the site has MFA enabled. Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel) ## Which versions are affected by CVE-2025-3639? 2 open source packages ship an affected version, including com.liferay.portal:release.portal.bom. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `com.liferay.portal:release.portal.bom` | Maven | From 7.3.0-ga1 to 7.4.3.132-ga132 | None | | `com.liferay.portal:release.portal.bom` | Maven | From 7.3.0-ga1 to 7.4.3.132-ga132 | None | ## How do I fix CVE-2025-3639? No fix has been published for CVE-2025-3639 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-3639 being exploited? There is no known exploitation of CVE-2025-3639 in the wild and no public exploit code. Public exploit code: - login bypass vulnerability in Liferay Portal (versions 7.3.0–7.4.3.132) and Liferay DXP (various versions from 2024.Q1 to 2025.Q1.6) (github_poc): https://github.com/6lj/CVE-2025-3639 ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-3639 and fix it if it is affected. What it is: CVE-2025-3639 is a low-severity authentication bypass vulnerability in Liferay DXP, published on 18 Aug 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2025-3639 in the wild and no public exploit code. Affected packages and fixed versions: - com.liferay.portal:release.portal.bom (Maven): affected from 7.3.0-ga1 up to 7.4.3.132-ga132; no fix listed - com.liferay.portal:release.portal.bom (Maven): affected from 7.3.0-ga1 up to 7.4.3.132-ga132; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-3639/ (Markdown: https://insights.sbomify.com/CVE-2025-3639/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-3639 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-3639 - OSV: https://osv.dev/vulnerability/CVE-2025-3639 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-3639/ Summaries are generated and may contain mistakes; the official description above is the record.