VulnerabilityPublished 3 Jun 2025

CVE-2025-41428: Keiyo System TimeWorks · Path Traversal

Affects Keiyo System TimeWorksSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.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 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/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 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 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
Keiyo System Co., LTD TimeWorks	Affected >=10.0 <=10.3	Fixed in–

AI-suggested

To mitigate CVE-2025-41428, European organizations should first identify all instances of TimeWorks versions 10.0 to 10.3 in their environment. Until an official patch is released by Keiyo System Co., LTD, organizations should implement compensating controls such as network-level restrictions to limit access to the TimeWorks server only to trusted internal IP addresses or VPN users. Web application firewalls (WAFs) can be configured to detect and block path traversal attack patterns in HTTP requests. Additionally, administrators should review and restrict file permissions on the server to minimize exposure of sensitive JSON files. Monitoring and logging access to these files can help detect suspicious activity. Organizations should engage with the vendor for patch availability and apply updates promptly once released. Conducting a thorough security assessment of TimeWorks deployments and isolating the application from critical network segments can further reduce risk. Finally, educating IT staff about this vulnerability and ensuring incident response plans are updated to address potential exploitation scenarios will enhance preparedness.

Description

Improper limitation of a pathname to a restricted directory ('Path Traversal') issue exists in TimeWorks 10.0 to 10.3. If exploited, arbitrary JSON files on the server may be viewed by a remote unauthenticated attacker.

Impact

For European organizations using TimeWorks versions 10.0 to 10.3, this vulnerability could lead to unauthorized disclosure of sensitive JSON files stored on the server. These files may contain configuration data, user information, scheduling details, or other business-critical information depending on how the software is deployed. Exposure of such data could facilitate further attacks, including social engineering, reconnaissance, or targeted exploitation of other systems. While the vulnerability does not allow modification or deletion of data, the confidentiality breach alone could violate data protection regulations such as GDPR, leading to legal and reputational consequences. Organizations in sectors with high privacy requirements, such as healthcare, finance, or government, may face increased risks. Additionally, since the vulnerability requires no authentication, it can be exploited by external attackers without insider access, increasing the attack surface. The lack of known exploits in the wild currently reduces immediate risk, but the medium severity rating and ease of exploitation warrant prompt attention.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Jul 2025, 07:05 UTC

Technical details

References

Community reviews

Related threats