VulnerabilityPublished 28 Jul 2025Updated 3 Nov 2025

CVE-2025-54768: Xorux LPAR2RRD · Incorrect Use of Privileged APIs

Affects Xorux LPAR2RRDSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 4.8% chance of exploitation in 30 days – higher than 92% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Xorux LPAR2RRD	Affected =8.04	Fixed in–

AI-suggested

Monitor Xorux communications and apply vendor-provided patches or updates as soon as they become available to address this vulnerability.
Implement strict network segmentation and firewall rules to restrict access to the LPAR2RRD web application and its API endpoints, limiting exposure to trusted administrative networks only.
Review and audit user roles and permissions within LPAR2RRD to ensure that read-only users cannot access privileged API endpoints.
Employ web application firewalls (WAF) with custom rules to detect and block unauthorized API calls targeting sensitive endpoints.
Conduct regular security assessments and penetration testing focused on API access controls to identify similar privilege escalation or information disclosure issues.
Monitor logs and alerts for unusual access patterns to the appliance configuration logs or API endpoints.
Educate administrators and users about the risks of exposing monitoring tools and enforce strong authentication and authorization policies.
If feasible, disable or restrict the vulnerable API endpoint until a patch is available.

Description

An API endpoint that should be limited to web application administrators is hidden from, but accessible by, lower-level read only web application users. The endpoint can be used to download logs from the appliance configuration, exposing sensitive information.

Impact

For European organizations, the exposure of sensitive appliance configuration logs could lead to information disclosure that aids attackers in mapping network infrastructure, identifying system weaknesses, or harvesting credentials and configuration details. This could facilitate subsequent targeted attacks, lateral movement, or data breaches. Organizations relying on LPAR2RRD for monitoring critical IBM Power Systems or virtualized environments may have sensitive operational data exposed to unauthorized users within their network or potentially from external sources if the application is internet-facing. While the vulnerability does not directly compromise system integrity or availability, the confidentiality breach can undermine trust and compliance with data protection regulations such as GDPR. The risk is heightened in sectors with stringent data privacy requirements, including finance, healthcare, and government agencies. Additionally, the ease of exploitation without authentication increases the threat level, especially in environments with weak network segmentation or insufficient internal access controls.

CWE-648Incorrect Use of Privileged APIs (opens in a new tab)
Base weaknessLikelihood of exploit: Low
The product does not conform to the API requirements for a function call that requires extra privileges. This could allow attackers to gain privileges by causing the function to be called incorrectly.
Implementation
Before calling privileged APIs, always ensure that the assumptions made by the privileged code hold true prior to making the call.
Architecture and Design
Know architecture and implementation weaknesses of the privileged APIs and make sure to account for these weaknesses before calling the privileged APIs to ensure that they can be called safely.
Implementation
If privileged APIs make certain assumptions about data, context or state validity that are passed by the caller, the calling code must ensure that these assumptions have been validated prior to making the call.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Cross Site Tracing (opens in a new tab)
Hijacking a privileged process (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2025, 01:41 UTC

WeaknessesCWE-648

Technical details

References

Community reviews

Related threats