CVE-2025-3760
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 · uneditedA stored cross-site scripting (XSS) vulnerability exists with radio button type custom fields in Liferay Portal 7.2.0 through 7.4.3.129, and Liferay DXP 2024.Q4.1 through 2024.Q4.7, 2024.Q3.1 through 2024.Q3.9, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.12, 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.10, 7.4 GA through update 92, 7.3 GA through update 36, and 7.2 GA through fix pack 20 allows remote authenticated attackers to inject malicious JavaScript into a page.
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in radio button type custom fields within Lifer Portal 7.2.0 through 7.4.3.129 and multiple Lifer DXP quarterly releases. Authenticated remote attackers can inject malicious JavaScript into custom field radio button values, which then executes in the browsers of other users who view pages containing these compromised fields.
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.2, <= 7.4>= 2023.Q3.0, < 2024.Q1.13>= 2024.q2.0, < 2024.q3.10>= 2024.Q4.0, < 2025.q1.0>= 7.2.0, <= 7.4.3.129CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 Lifer Portal/DXP versionNavigate to Lifer Control Panel > Configuration > Server Information, or query the Lifer API endpoint /api/jsonws/systeminfo/get-system-info to retrieve the installed versionAffected if The installed version falls within 7.2.0 to 7.4.3.129 for Lifer Portal, or matches the DXP quarterly ranges: >= 2023.Q3.0 and < 2024.Q1.13, >= 2024.Q2.0 and < 2024.Q3.10, or >= 2024.Q4.0 and < 2025.Q1.0
-
Locate custom fields of radio button typeIn Lifer Control Panel, go to Configuration > Custom Fields > Object Fields, or query the ObjectField table in the database filtering by fieldType = 'radio' or similar designation for radio button fieldsAffected if Any radio button type custom fields are defined in the system
-
Inspect radio button custom field values for suspicious contentQuery the custom field value storage (CustomFieldValue table or equivalent) for radio button fields and examine the value column for script tags, javascript: prefixes, event handlers (onclick, onerror, etc.), or encoded payloadsAffected if Any radio button custom field values contain HTML script tags, javascript: protocols, or known XSS payloads
-
Verify user permissions for custom field modificationReview Lifer roles and permissions under Control Panel > Users > Roles, specifically checking which roles have permissions to create or edit custom fields (e.g., Object Field: Update, Object Field: Add Object Field)Affected if Users other than administrators or high-privilege roles have permissions to modify custom field definitions containing radio button options
The environment is affected if running a vulnerable Lifer Portal/DXP version AND radio button custom fields are present with potentially injected malicious values or with edit access granted to lower-privilege users.
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 · scoped2024.Q1.132024.q3.102025.q1.0
Upgrade to the latest Lifer DXP/Portal version or apply available security patches. Additionally, implement proper input validation and output encoding for all custom field radio button values to prevent XSS execution.
Liferay DXP/Portal: Upgrade to the first version past your current release as listed in the official description (e.g., 2024.Q4.8, 2024.Q3.10, 2024.Q2.14, 2024.Q1.13, 2023.Q4.11, 2023.Q3.11, or Portal updates 93/37/fix pack 21)
- 1. Identify your current Liferay Portal or DXP version from the Liferay Control Panel or version metadata
- 2. For Liferay DXP 2024.Q4.x users: Upgrade to version 2024.Q4.8 or later
- 3. For Liferay DXP 2024.Q3.x users: Upgrade to version 2024.Q3.10 or later
- 4. For Liferay DXP 2024.Q2.x users: Upgrade to version 2024.Q2.14 or later
- 5. For Liferay DXP 2024.Q1.x users: Upgrade to version 2024.Q1.13 or later
- 6. For Liferay DXP 2023.Q4.x users: Upgrade to version 2023.Q4.11 or later
- 7. For Liferay DXP 2023.Q3.x users: Upgrade to version 2023.Q3.11 or later
- 8. For Liferay Portal 7.4.x users: Upgrade to update 93 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3760 — 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-3760 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