CVE-2025-4576
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 reflected cross-site scripting (XSS) vulnerability in the Liferay Portal 7.4.0 through 7.4.3.133, and Liferay DXP 2025.Q1.0 through 2025.Q1.4 ,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 allows an remote non-authenticated attacker to inject JavaScript into the modules/apps/blogs/blogs-web/src/main/resources/META-INF/resources/blogs/entry_cover_image_caption.jsp
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 reflected cross-site scripting (XSS) vulnerability exists in the entry_cover_image_caption.jsp file of Lifer Portal 7.4.0-7.4.3.133 and Lifer DXP (multiple quarterly versions from 2024.Q1 through 2025.Q1). A remote unauthenticated attacker can inject malicious JavaScript via this endpoint.
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>= 2024.q1.1, <= 2024.q1.15>= 2024.q2.0, <= 2024.q2.13>= 2024.q3.1, <= 2024.q3.13>= 2024.q4.0, <= 2024.q4.7>= 2025.q1.0, <= 2025.q1.4= 7.4>= 7.4.0, <= 7.4.3.133CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 installed Lifer Portal versionCheck the portal's version information typically found in the control panel under Server Information, or inspect the portal-impl.jar MANIFEST.MF file, or look at the osgi/state directory for version metadataAffected if The version falls within 7.4.0 through 7.4.3.133 for Lifer Portal, or within the affected DXP quarterly ranges (2024.q1.1-2024.q1.15, 2024.q2.0-2024.q2.13, 2024.q3.1-2024.q3.13, 2024.q4.0-2024.q4.7, or 2025.q1.0-2025.q1.4)
-
Locate the vulnerable JSP fileSearch for entry_cover_image_caption.jsp in the deployed web application directory, typically under ROOT/webapp or the theme webapp folderAffected if The file exists in the deployed application and is accessible via the web server
-
Verify the endpoint accepts unsanitized inputSend a crafted HTTP request to the endpoint with a test XSS payload in the caption parameter, such as ?caption=<script>alert(1)</script>, and observe if the script tag is reflected in the response without encodingAffected if The injected JavaScript payload is reflected in the HTTP response without HTML encoding or sanitization, indicating the XSS vulnerability is present and exploitable
A user is affected if their Lifer Portal or DXP version falls within the specified ranges AND the entry_cover_image_caption.jsp endpoint reflects unsanitized user input in its response.
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.
From vendor dataApply the vendor-provided security patch or upgrade to a fixed Lifer version. If immediate patching is not possible, implement input validation and output encoding on the affected JSP endpoint.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4576 — 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-4576 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