CVE-2025-5545VulnerabilityPublished 3 Jun 2025

CVE-2025-5545: aaluoxiang oa_system · Path Traversal

Affects aaluoxiang oa_systemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system 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 Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Jun 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 2026-10-25.

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 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

AI-suggested

To mitigate CVE-2025-5545, European organizations should first conduct a thorough inventory to identify deployments of the aaluoxiang oa_system, especially those exposed to external networks. Since no official patches or versioning information are available, organizations should implement compensating controls such as web application firewalls (WAFs) configured to detect and block path traversal patterns (e.g., ../ sequences) in HTTP requests targeting the vulnerable endpoint. Network segmentation should be enforced to limit access to the oa_system from untrusted networks. Access controls and least privilege principles should be applied to the oa_system server to minimize the impact of potential data disclosure. Monitoring and logging of file access and unusual request patterns should be enhanced to detect exploitation attempts early. If possible, source code review and custom patching of the ProcedureController.java image function to properly validate and sanitize file path inputs should be undertaken. Organizations should engage with the vendor or community for updates or patches and consider alternative solutions if remediation is not feasible. Regular security assessments and penetration testing focusing on path traversal and input validation vulnerabilities are recommended.

Description

A vulnerability classified as problematic has been found in aaluoxiang oa_system up to 5b445a6227b51cee287bd0c7c33ed94b801a82a5. This affects the function image of the file src/main/java/cn/gson/oasys/controller/process/ProcedureController.java. The manipulation leads to path traversal. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable.

Impact

For European organizations using the aaluoxiang oa_system, this vulnerability poses a moderate risk primarily related to unauthorized information disclosure. Attackers exploiting the path traversal could access sensitive internal files, potentially exposing confidential business data, user credentials, or system configuration details. This could facilitate further attacks such as privilege escalation or lateral movement within the network. Given the remote attack vector and no requirement for user interaction, exploitation could be automated and widespread if the product is deployed in internet-facing environments. The medium severity score reflects limited direct impact on system integrity or availability but significant confidentiality concerns. Organizations in sectors with strict data protection regulations, such as finance, healthcare, and government, could face compliance risks and reputational damage if sensitive data is leaked. Additionally, the absence of versioning and patch information complicates timely remediation, increasing exposure duration. The impact is heightened if the oa_system is integrated with critical business workflows or contains sensitive operational data.

Summary

CVE-2025-5545 is a path traversal vulnerability identified in the aaluoxiang oa_system product, specifically affecting the image function within the ProcedureController.java source file. This vulnerability allows an unauthenticated remote attacker with low privileges to manipulate file paths in such a way that they can access files outside the intended directory structure. The vulnerability arises due to insufficient validation or sanitization of user-supplied input used in file path construction, enabling traversal sequences (e.g., ../) to access arbitrary files on the server. The affected version is identified by a commit hash (5b445a6227b51cee287bd0c7c33ed94b801a82a5), and since the product does not use versioning, it is unclear which other versions might be impacted. The CVSS 4.0 base score is 5.3 (medium severity), with an attack vector of network (remote), low attack complexity, no privileges required, no user interaction, and low impact on confidentiality. No known exploits are currently in the wild, but public disclosure of the vulnerability exists, increasing the risk of exploitation. The lack of versioning and patch information complicates mitigation efforts. The vulnerability could allow attackers to read sensitive files, potentially exposing configuration files, credentials, or other sensitive data, which could lead to further compromise if leveraged in chained attacks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 4 Jul 2025, 21:27 UTC

Technical details

References

Community reviews

Related threats