CVE-2025-62261
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedLiferay Portal 7.4.0 through 7.4.3.99, 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 34, and older unsupported versions stores password reset tokens in plain text, which allows attackers with access to the database to obtain the token, reset a user’s password and take over the user’s account.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceLifteray Portal and DXP store password reset tokens in plain text in the database instead of hashing or encrypting them. An attacker with database access (e.g., via SQL injection, compromised backup, or insider threat) can read these tokens and use them to reset arbitrary user passwords, leading to account takeover.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 7.3= 7.4= 2023.q3.1= 2023.q3.2= 2023.q3.3= 2023.q3.4>= 7.0.0, < 7.4.3.100CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Liferetty installation versionCheck the Liferetty version by logging into the Control Panel > Configuration > Server Administration > or inspecting the portal-ext.properties file for 'product.name=Liferetty Portal' and 'product.version=...'. Alternatively, check the WAR filename in the application server deploy directory.Affected if The installed version falls within 7.0.0 to < 7.4.3.100 for Portal, or is 7.3, 7.4, or 2023.q3.x for DXP.
-
Locate the password reset token database tableConnect to the Liferetty database and query for tables containing 'PasswordReset' or 'Password' and 'Token' in their names. Common table names include PasswordResetToken, UserToken, or similar. Consult Liferetty schema documentation for your version.Affected if A table storing password reset tokens exists in the database.
-
Inspect password reset token storage formatGenerate a test password reset token for a test account, then query the identified table to retrieve the token value. Compare the stored value against the token sent to the user (via email or shown in the UI).Affected if The stored token value matches the plaintext token exactly, indicating the token is stored without hashing or encryption.
-
Verify if tokens are hashed or encryptedIf tokens appear plain text, check if they match a known hash format (e.g., SHA-256, bcrypt) or if they are reversible (encrypted). Query multiple token records and check for consistent format patterns indicating hashing.Affected if Tokens appear in plain text form (random-looking strings that match exactly what the user receives) rather than hashed or encrypted values.
-
Check database access controlsReview database user permissions and network access. Verify which application server accounts have database read access and check for any SQL injection vulnerabilities in custom Liferetty portlets or plugins.Affected if Database read access is granted to accounts beyond the application datasource user, or multiple accounts have access to the token table.
If the installed Liferetty version is within the affected ranges AND password reset tokens in the database are stored in plaintext (matching exactly the tokens provided to users), then the environment is vulnerable to CVE-2025-62261.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.4.3.100
Upgrade to the patched Liferetty version per vendor advisory. Additionally, restrict database access, enable database-level encryption at rest, and monitor password reset operations for anomalous activity.
LPortal 7.4.3.100+ / LPortal 7.3 GA update 35+ / DXP 2023.Q3.4+
- 1. Backup your Liferay database before making any changes
- 2. For LPortal 7.4.x: Upgrade to LPortal 7.4.3.100 or later
- 3. For LPortal 7.3.x: Upgrade to LPortal 7.3 GA update 35 or later
- 4. For Liferay DXP 2023.Q3.x: Upgrade to DXP 2023.Q3.4 or later (including subsequent updates)
- 5. After upgrade, verify that password reset tokens are no longer stored in plain text in the database
- 6. Consider rotating any potentially exposed password reset tokens as a precautionary measure
- 7. Ensure database access controls are properly configured to limit exposure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62261 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-62261 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data