CVE-2025-11565
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 · uneditedCWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability exists that could cause elevated system access when a Web Admin user on the local network tampers with the POST /REST/UpdateJRE request payload.
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 path traversal vulnerability in the /REST/UpdateJRE endpoint allows authenticated Web Admin users on the local network to manipulate file paths in the POST request payload using '../' sequences, potentially escaping restricted directories to gain elevated system access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Local
- Complexity
- High
- Privileges
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 product and installed versionLocate the product's version information through its web interface, admin panel, or system files (check /opt/vendor/version, registry, or built-in 'about' page)Affected if Version cannot be determined or is unknown - compare against any vendor-released advisory for affected version ranges
-
Confirm /REST/UpdateJRE endpoint is accessibleAttempt to reach the endpoint via HTTP/HTTPS request (e.g., GET https://target/REST/UpdateJRE) or examine the application's exposed API routesAffected if Endpoint returns a valid response (200/401/403) indicating it exists and is exposed
-
Verify Web Admin authentication is configuredCheck if Web Admin user accounts are enabled in the system configuration; look for admin login pages, user management settings, or authentication-related config filesAffected if Web Admin authentication is enabled and local network users can authenticate to the admin interface
-
Assess local network exposureReview firewall rules, network ACLs, or interface bindings to determine if the management interface is accessible from the local network rather than localhost onlyAffected if The web admin interface is reachable from network addresses other than 127.0.0.1 or ::1
-
Inspect request handling for path traversal protectionExamine server logs or HTTP traffic for POST requests to /REST/UpdateJRE containing '../' sequences in file path parameters; check if requests are logged, allowed, or rejectedAffected if Path traversal sequences in requests to UpdateJRE are not blocked or sanitized by the server
A user is affected if the product exposes the /REST/UpdateJRE endpoint to authenticated Web Admin users on the local network without path traversal validation on file path parameters.
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 dataImplement strict input validation and path sanitization on the UpdateJRE endpoint to ensure all file paths are constrained to allowed directories, rejecting any requests containing path traversal sequences.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11565 — 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-11565 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