CVE-2025-54812 Vulnerability Analysis & Exploit Details

CVE-2025-54812
Vulnerability Scoring

5.4
/10
Significant Risk

Security assessments indicate that CVE-2025-54812 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Changed
    Successful exploitation can impact components beyond the vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2025-54812 Details

Status: Analyzed

Last updated: 🕘 26 Aug 2025, 21:16 UTC
Originally published on: 🕖 22 Aug 2025, 19:15 UTC

Time between publication and last update: 4 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2025-54812 Vulnerability Summary

CVE-2025-54812: Improper Output Neutralization for Logs vulnerability in Apache Log4cxx. When using HTMLLayout, logger names are not properly escaped when writing out to the HTML file. If untrusted data is used to retrieve the name of a logger, an attacker could theoretically inject HTML or Javascript in order to hide information from logs or steal data from the user. In order to activate this, the following sequence must occur: * Log4cxx is configured to use HTMLLayout. * Logger name comes from an untrusted string * Logger with compromised name logs a message * User opens the generated HTML log file in their browser, leading to potential XSS Because logger names are generally constant strings, we assess the impact to users as LOW This issue affects Apache Log4cxx: before 1.5.0. Users are recommended to upgrade to version 1.5.0, which fixes the issue.

Assessing the Risk of CVE-2025-54812

Access Complexity Graph

The exploitability of CVE-2025-54812 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2025-54812

CVE-2025-54812 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2025-54812, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2025-54812, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2025-54812 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2025-54812 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2025-54812 does not impact system availability.

CVE-2025-54812 References

External References

CWE Common Weakness Enumeration

CWE-117

CAPEC Common Attack Pattern Enumeration and Classification

  • Audit Log Manipulation CAPEC-268 The attacker injects, manipulates, deletes, or forges malicious log entries into the log file, in an attempt to mislead an audit of the log file or cover tracks of an attack. Due to either insufficient access controls of the log files or the logging mechanism, the attacker is able to perform such actions.
  • Web Server Logs Tampering CAPEC-81 Web Logs Tampering attacks involve an attacker injecting, deleting or otherwise tampering with the contents of web logs typically for the purposes of masking other malicious behavior. Additionally, writing malicious data to log files may target jobs, filters, reports, and other agents that process the logs in an asynchronous attack pattern. This pattern of attack is similar to "Log Injection-Tampering-Forging" except that in this case, the attack is targeting the logs of the web server and not the application.
  • Log Injection-Tampering-Forging CAPEC-93 This attack targets the log files of the target host. The attacker injects, manipulates or forges malicious log entries in the log file, allowing them to mislead a log audit, cover traces of attack, or perform other malicious actions. The target host is not properly controlling log access. As a result tainted data is resulting in the log files leading to a failure in accountability, non-repudiation and incident forensics capability.

Vulnerable Configurations

  • cpe:2.3:a:apache:log4cxx:-:*:*:*:*:*:*:*
    cpe:2.3:a:apache:log4cxx:-:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:log4cxx:0.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:log4cxx:0.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:log4cxx:0.10.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:apache:log4cxx:0.10.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:apache:log4cxx:0.10.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:apache:log4cxx:0.10.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:apache:log4cxx:0.10.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:apache:log4cxx:0.10.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:apache:log4cxx:0.10.0:rc4:*:*:*:*:*:*
    cpe:2.3:a:apache:log4cxx:0.10.0:rc4:*:*:*:*:*:*
  • cpe:2.3:a:apache:log4cxx:0.10.0:rc5:*:*:*:*:*:*
    cpe:2.3:a:apache:log4cxx:0.10.0:rc5:*:*:*:*:*:*
  • cpe:2.3:a:apache:log4cxx:0.10.0:rc6:*:*:*:*:*:*
    cpe:2.3:a:apache:log4cxx:0.10.0:rc6:*:*:*:*:*:*
  • cpe:2.3:a:apache:log4cxx:0.10.0:rc7:*:*:*:*:*:*
    cpe:2.3:a:apache:log4cxx:0.10.0:rc7:*:*:*:*:*:*
  • cpe:2.3:a:apache:log4cxx:0.10.0:rc8:*:*:*:*:*:*
    cpe:2.3:a:apache:log4cxx:0.10.0:rc8:*:*:*:*:*:*
  • cpe:2.3:a:apache:log4cxx:0.11.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:log4cxx:0.11.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:log4cxx:0.11.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:apache:log4cxx:0.11.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:apache:log4cxx:0.12.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:log4cxx:0.12.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:log4cxx:0.12.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:apache:log4cxx:0.12.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:apache:log4cxx:0.12.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:apache:log4cxx:0.12.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:apache:log4cxx:0.12.1:rc1:*:*:*:*:*:*
    cpe:2.3:a:apache:log4cxx:0.12.1:rc1:*:*:*:*:*:*
  • cpe:2.3:a:apache:log4cxx:0.13.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:log4cxx:0.13.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:log4cxx:0.13.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:apache:log4cxx:0.13.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:apache:log4cxx:1.0.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:apache:log4cxx:1.0.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:apache:log4cxx:1.1.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:log4cxx:1.1.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:log4cxx:1.1.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:apache:log4cxx:1.1.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:apache:log4cxx:1.1.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:apache:log4cxx:1.1.0:rc2:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2025-54812: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-41708 – Due to an unsecure default configuration HTTP is used instead of HTTPS for the web interface. An unauthenticated attacker on the same network could...
  • CVE-2025-41682 – An authenticated, low-privileged attacker can obtain credentials stored on the charge controller including the manufacturer password.
  • CVE-2025-41664 – A low-privileged remote attacker could gain unauthorized access to critical resources, such as firmware and certificates, due to improper permissio...
  • CVE-2025-10088 – A vulnerability was detected in SourceCodester Time Tracker 1.0. The affected element is an unknown function of the file /index.html. Performing ma...
  • CVE-2025-10087 – A security vulnerability has been detected in SourceCodester Pet Grooming Management Software 1.0. Impacted is an unknown function of the file /adm...