CVE-2025-1534
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 · uneditedCVE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Payara Platform Payara Server allows : Remote Code Inclusion.This issue affects Payara Server: from 4.1.2.1919.1 before 4.1.2.191.51, from 5.20.0 before 5.68.0, from 6.0.0 before 6.23.0, from 6.2022.1 before 6.2025.2.
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 · moderate confidenceA cross-site scripting (XSS) vulnerability in Payara Server's web interface allows attackers to inject malicious scripts into pages generated by the application. The description mentions 'Remote Code Inclusion' as a potential impact, though the medium CVSS score suggests limited scope.
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>= 4.1.2.191.1, < 4.1.2.191.51>= 5.20.0, < 5.68.0>= 6.0.0, < 6.24.0>= 6.2022.1, < 6.2025.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.
-
Identify Payara Server versionRun 'asadmin version' command from the Payara installation bin directory, or check the startup log file (usually named server.log) for the Payara version printed during server startup.Affected if The installed version falls within one of these ranges: 4.1.2.191.1 through 4.1.2.191.50, 5.20.0 through 5.67.0, 6.0.0 through 6.23.0, or 6.2022.1 through 6.2025.2
-
Verify admin web console is accessibleAttempt to reach the Payara admin console in a browser at the default URL (typically http://localhost:4848 or https://localhost:4848 for the secure port). Confirm the login page or console loads successfully.Affected if The admin console is accessible and the Payara version from step 1 is in the affected ranges listed above.
-
Check for recent XSS indicators in logsReview Payara server log files (server.log) for suspicious patterns in HTTP requests that may indicate exploitation attempts, such as script tags, javascript: URIs, or other XSS payloads in request parameters.Affected if The server version is affected AND anomalous XSS-like request patterns appear in the logs.
You are affected if your Payara Server version is within the vulnerable ranges AND the admin web console is accessible on your network.
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 · scoped4.1.2.191.515.68.06.24.0
Upgrade Payara Server to version 4.1.2.191.51, 5.68.0, 6.23.0, or 6.2025.2 or later. If immediate upgrade is not possible, implement web application firewall rules to filter malicious script payloads in HTTP requests.
4.1.2.191.51 (for 4.1.2.x); 5.68.0 (for 5.x); 6.24.0 (for 6.0.x-6.23.x); 6.2025.3 (for 6.2022.x)
- 1. Identify the currently installed Payara Server version using the admin console or asadmin version command
- 2. Determine which version branch your installation belongs to (4.1.2.x, 5.x, 6.0.x-6.23.x, or 6.2022.x)
- 3. For Payara 4.1.2.x branch: upgrade to version 4.1.2.191.51 or later
- 4. For Payara 5.x branch: upgrade to version 5.68.0 or later
- 5. For Payara 6.0.x to 6.23.x branch: upgrade to version 6.24.0 or later
- 6. For Payara 6.2022.x branch: upgrade to version 6.2025.3 or later
- 7. Download the new version from the official Payara download page (www.payara.fish/software/payara-server/)
- 8. Back up your current Payara installation including domain configurations and deployed applications
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1534 — 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-1534 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