VulnerabilityPublished 27 Oct 2025

CVE-2025-12250: OpenWGA · Path Traversal

Affects OpenWGASource CVE Database V5

Public exploit available · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

5.1Medium

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

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

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

Base metrics

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

Threat metrics

Exploit Maturity: POC

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: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, 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

AI-suggested

Immediately restrict network access to OpenWGA instances running version 7.11.12 Build 737, especially from untrusted networks or the internet.
Implement strict input validation and sanitization on all file path parameters processed by the TMLScript API to prevent path traversal attempts.
Employ application-layer firewalls or web application firewalls (WAFs) with custom rules to detect and block path traversal payloads targeting OpenWGA.
Isolate OpenWGA servers in segmented network zones with limited access to sensitive backend systems and files.
Monitor logs for suspicious file access patterns indicative of path traversal exploitation attempts.
Engage with the vendor or community to obtain updates or patches as soon as they become available.
Consider upgrading to a newer, unaffected version of OpenWGA once a patch is released.
Conduct regular security assessments and penetration tests focusing on file handling components of OpenWGA.
Educate system administrators about the vulnerability and the importance of applying mitigations promptly.

Description

A flaw has been found in OpenWGA 7.11.12 Build 737. This affects an unknown function of the file WGA.File of the component TMLScript API. Executing manipulation can lead to path traversal. It is possible to launch the attack remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, this vulnerability poses a risk of unauthorized access to sensitive files hosted on OpenWGA servers, potentially exposing confidential business information, user data, or internal configurations. The ability to remotely exploit the flaw without user interaction increases the threat surface, especially in environments where OpenWGA is exposed to the internet or accessible by multiple users. Although exploitation requires high privileges, attackers who have already gained elevated access (e.g., through other vulnerabilities or insider threats) can leverage this flaw to escalate their impact. This could lead to data breaches, disruption of web services, or further lateral movement within networks. The absence of vendor patches and the presence of public exploits heighten the urgency for European organizations to implement compensating controls. The impact is particularly significant for sectors with stringent data protection requirements, such as finance, healthcare, and government institutions within Europe.

Summary

CVE-2025-12250 is a path traversal vulnerability identified in OpenWGA version 7.11.12 Build 737, specifically within the TMLScript API's WGA.File component. Path traversal vulnerabilities allow attackers to manipulate file path inputs to access files and directories outside the intended scope, potentially exposing sensitive data or configuration files. This vulnerability can be exploited remotely without user interaction, but requires the attacker to have high privileges on the system, which limits the ease of exploitation to some extent. The vulnerability impacts confidentiality by allowing unauthorized file access and integrity by potentially enabling attackers to read or modify critical files. The vendor has not responded to early disclosure attempts, and no official patches have been released, although a public exploit is available, increasing the risk of exploitation. The CVSS 4.0 score is 5.1 (medium), reflecting network attack vector, low complexity, no user interaction, but requiring high privileges and causing low impact on confidentiality, integrity, and availability. The lack of vendor response and patch availability means organizations must rely on mitigations such as access restrictions and input validation. OpenWGA is a web content management system used in various enterprise environments, making this vulnerability relevant to organizations relying on it for internal or external web services.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 3 Nov 2025, 09:23 UTC

Technical details

References

Community reviews

Related threats