CVE-2024-25603
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 the Dynamic Data Mapping module's DDMForm in Liferay Portal 7.2.0 through 7.4.3.4, and older unsupported versions, and Liferay DXP 7.4.13, 7.3 before update 4, 7.2 before fix pack 17, and older unsupported versions allows remote authenticated users to inject arbitrary web script or HTML via the instanceId parameter.
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 XSS vulnerability in Liferays Dynamic Data Mapping (DDM) Form module allows authenticated users to inject malicious scripts via the unsanitized instanceId parameter. The injected payload persists and executes when other users view the affected DDMForm, enabling session hijacking, credential theft, or defacement.
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.0, < 7.4.3.5< 7.2= 7.2= 7.3= 7.4CVSS 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.
-
Check Liferay Portal versionAccess Liferay portal administration and navigate to Control Panel > Configuration > Server Administration > Product Information, or query the Liferay database for the portal version. Compare the installed version number against the affected ranges: >= 7.2.0 and < 7.4.3.5 for Liferay Portal.Affected if The installed version falls within >= 7.2.0 to < 7.4.3.5 for Liferay Portal, or matches DXP versions 7.2, 7.3, or 7.4 as listed in affected products.
-
Confirm DDM Form module is in useIn Liferay admin, navigate to Content > Data Definition or search for Dynamic Data Mapping forms in the site or global scope. Check if any DDMForm structures or templates exist in the system.Affected if DDM Form structures or templates are created and stored in the Liferay instance.
-
Inspect DDMForm instanceId parameter valuesAccess the Liferay database and query the DDMForm or DDMFormStructure tables for the instanceId field. For example: SELECT * FROM DDMForm WHERE instanceId IS NOT NULL; or examine the form's JSON/XML configuration where instanceId is stored. Alternatively, use Liferay's JSON web services API to retrieve DDMForm definitions.Affected if Any DDMForm record contains an unsanitized instanceId value containing script tags, event handlers, or suspicious encoded characters that could execute as JavaScript.
-
Verify form accessibility to other usersCheck the permissions on identified DDM Forms to determine if they are accessible to authenticated users other than the creator. Review the DDMForm's sharing settings, site membership, or role permissions in the Liferay control panel under the specific form's permissions.Affected if The affected DDMForm with the malicious instanceId is accessible to multiple users, allowing the stored XSS to execute when they view the form.
Your environment is affected if you run a Liferay Portal version between 7.2.0 and 7.4.3.5 (or DXP 7.2/7.3/7.4), have DDM Forms in use, and any DDMForm record contains unsanitized instanceId values accessible to multiple 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 · scoped7.27.4.3.5
Apply vendor-provided patches or upgrade to Liferays patched versions: Portal 7.4.3.5+, DXP 7.4.13 GA+, DXP 7.3 update 4+, DXP 7.2 fix pack 17+. Implement output encoding on the instanceId field as defense-in-depth.
Liffel Portal >= 7.4.3.5; Liffel DXP 7.2 >= Fix Pack 17; Liffel DXP 7.3 >= Update 4; Liffel DXP >= 7.4.13 GA
- 1. Identify the current Liffel Portal or DXP version by navigating to Control Panel > Configuration > Server Administration > Platform Information
- 2. For Liffel Portal 7.2.0-7.4.3.4: Upgrade to Liffel Portal 7.4.3.5 or later
- 3. For Liffel DXP 7.2: Apply Fix Pack 17 or later
- 4. For Liffel DXP 7.3: Apply Update 4 or later
- 5. For Liffel DXP 7.4: Upgrade to a version greater than 7.4.13 (e.g., 7.4.13 GA or later fixed release)
- 6. After upgrading, verify the DDMForm instanceId parameter is no longer vulnerable by testing with benign XSS payloads
- 7. Review Liffel release notes and Known Issues for the target version before production deployment
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-2024-25603 — 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-25603 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