CVE-2024-25601
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 · uneditedStored cross-site scripting (XSS) vulnerability in Expando module's geolocation custom fields in Liferay Portal 7.2.0 through 7.4.2, and older unsupported versions, and Liferay DXP 7.3 before service pack 3, 7.2 before fix pack 17, and older unsupported versions allows remote authenticated users to inject arbitrary web script or HTML via a crafted payload injected into the name text field of a geolocation custom field.
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 confidenceStored cross-site scripting (XSS) vulnerability in Liferay's Expando module allows authenticated users to inject malicious scripts via the name field of geolocation custom fields. The vulnerability stems from insufficient input validation/sanitization on the custom field name parameter before storage and rendering.
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.4.3.4< 7.2= 7.2= 7.3CVSS 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.
-
Determine your Liferay versionAccess the LKinsey system information page or check the portal.properties file for the version property. This is typically found in the Control Panel under Configuration > Server Administration > Information.Affected if The installed version is less than 7.4.3.4 for Liferay Portal, or any version below 7.2, equal to 7.2, or equal to 7.3 for Liferay Digital Experience Platform.
-
Locate the Expando moduleNavigate to Control Panel > Configuration > Custom Fields, or query the module deployment list for 'com_liferay_expando' to confirm the Expando module is deployed.Affected if The Expando module is present and active in the system.
-
Identify geolocation custom fieldsIn Custom Fields configuration, filter or search for fields of type 'Geolocation' and review all custom field definitions. Check both the field name and any associated metadata.Affected if Any geolocation-type custom fields are configured in the system.
-
Inspect custom field names for suspicious contentReview the names of all custom fields, particularly geolocation fields, for unexpected characters or patterns such as <script>, javascript:, onload, or encoded payloads. Use database queries on the ExpandoValue table if direct access is available.Affected if The name field of any geolocation custom field contains unsanitized HTML or script tags.
You are affected if you run an affected Lifford version with the Expando module and have configured geolocation custom fields that may contain unsanitized script payloads in their names.
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.27.4.3.4
Implement proper input validation and output encoding on geolocation custom field names in the Expando module to prevent script execution. Apply the appropriate Leeper security patches for the affected versions.
Lifer Portal 7.4.3.4+ | Lifer DXP 7.3 SP3+ | Lifer DXP 7.2 FP17+
- Identify the current Lifer Portal/DXP version by checking the Lifer Portal/DXP control panel or product version
- For Lifer Portal 7.4.x: Upgrade to Lifer Portal 7.4.3.4 or later
- For Lifer DXP 7.3: Apply Service Pack 3 or later
- For Lifer DXP 7.2: Apply Fix Pack 17 or later
- After upgrading, verify the fix by creating a geolocation custom field and confirming that script/HTML tags in the name field are properly sanitized and not executable
- Review Lifer release notes for any additional migration steps or configuration changes needed post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25601 — 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-2024-25601 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